diff options
| author | Peter Eisentraut <peter_e@gmx.net> | 2013-10-07 22:41:53 -0400 |
|---|---|---|
| committer | Peter Eisentraut <peter_e@gmx.net> | 2013-10-07 22:41:53 -0400 |
| commit | 4a72c60e4a4ab3b60c809079924d019367428315 (patch) | |
| tree | 00bc82b0818145c795538f9b87ba480ea3a1a14f | |
| parent | 791a71a679970c801f526c6b2bb5ef51d6c21ec5 (diff) | |
| download | postgresql-4a72c60e4a4ab3b60c809079924d019367428315.tar.gz postgresql-4a72c60e4a4ab3b60c809079924d019367428315.zip | |
Revert "Document support for VPATH builds of extensions."
This reverts commit 6ed3c5f7b2846be9e176ea1c99b2d45bba0d6972.
| -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 7db906aebb6..b571b5f66bf 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -928,7 +928,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 @@ -1165,33 +1165,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 |