diff options
| author | Peter Eisentraut <peter_e@gmx.net> | 2013-10-07 22:42:52 -0400 |
|---|---|---|
| committer | Peter Eisentraut <peter_e@gmx.net> | 2013-10-07 22:42:52 -0400 |
| commit | 4e80950042ff70a8d9825c1d9549692b8124dd40 (patch) | |
| tree | 70bb1b29d9fbdd3fd39571b60a6a1c30f6b0cf80 | |
| parent | 9fba0cbee38bd73b68ed350c31eee3bb102bd422 (diff) | |
| download | postgresql-4e80950042ff70a8d9825c1d9549692b8124dd40.tar.gz | |
Revert "Document support for VPATH builds of extensions."
This reverts commit 9598134e3030a883ff6eea8a822466ce5143ffeb.
| -rw-r--r-- | doc/src/sgml/extend.sgml | 29 |
1 files changed, 1 insertions, 28 deletions
diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 5015002aac..60fa1a8922 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -935,7 +935,7 @@ include $(PGXS) To use the <acronym>PGXS</acronym> infrastructure for your extension, you must write a simple makefile. In the makefile, you need to set some variables - and include the global <acronym>PGXS</acronym> makefile. + and finally include the global <acronym>PGXS</acronym> makefile. Here is an example that builds an extension module named <literal>isbn_issn</literal>, consisting of a shared library containing some C code, an extension control file, a SQL script, and a documentation @@ -1172,33 +1172,6 @@ include $(PGXS) </caution> <para> - You can also run <literal>make</literal> in a directory outside the source - tree of your extension, if you want to keep the build directory separate. - This procedure is also called a - <indexterm><primary>VPATH</primary></indexterm><firstterm>VPATH</firstterm> - build. Here's how: - <screen> - <userinput>mkdir build_dir</userinput> - <userinput>cd build_dir</userinput> - <userinput>make -f /path/to/extension/source/tree/Makefile</userinput> - <userinput>make -f /path/to/extension/source/tree/Makefile install</userinput> - </screen> - </para> - - <para> - Alternatively, you can set up a directory for a VPATH build in a similar - way to how it is done for the core code. One way to to this is using the - core script <filename>config/prep_buildtree</>. Once this has been done - you can build by setting the <literal>make</literal> variable - <varname>USE_VPATH</varname> like this: - <screen> - <userinput>make USE_VPATH=/path/to/extension/source/tree</userinput> - <userinput>make USE_VPATH=/path/to/extension/source/tree install</userinput> - </screen> - This procedure can work with a greater variety of directory layouts. - </para> - - <para> The scripts listed in the <varname>REGRESS</> variable are used for regression testing of your module, which can be invoked by <literal>make installcheck</literal> after doing <literal>make install</>. For this to |