From 4a72c60e4a4ab3b60c809079924d019367428315 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Mon, 7 Oct 2013 22:41:53 -0400 Subject: [PATCH] Revert "Document support for VPATH builds of extensions." This reverts commit 6ed3c5f7b2846be9e176ea1c99b2d45bba0d6972. --- doc/src/sgml/extend.sgml | 29 +---------------------------- 1 file changed, 1 insertion(+), 28 deletions(-) diff --git a/doc/src/sgml/extend.sgml b/doc/src/sgml/extend.sgml index 7db906aebb..b571b5f66b 100644 --- a/doc/src/sgml/extend.sgml +++ b/doc/src/sgml/extend.sgml @@ -928,7 +928,7 @@ include $(PGXS) To use the PGXS infrastructure for your extension, you must write a simple makefile. In the makefile, you need to set some variables - and include the global PGXS makefile. + and finally include the global PGXS makefile. Here is an example that builds an extension module named isbn_issn, consisting of a shared library containing some C code, an extension control file, a SQL script, and a documentation @@ -1164,33 +1164,6 @@ include $(PGXS) - - You can also run make 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 - VPATHVPATH - build. Here's how: - - mkdir build_dir - cd build_dir - make -f /path/to/extension/source/tree/Makefile - make -f /path/to/extension/source/tree/Makefile install - - - - - 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 config/prep_buildtree. Once this has been done - you can build by setting the make variable - USE_VPATH like this: - - make USE_VPATH=/path/to/extension/source/tree - make USE_VPATH=/path/to/extension/source/tree install - - This procedure can work with a greater variety of directory layouts. - - The scripts listed in the REGRESS variable are used for regression testing of your module, which can be invoked by make -- 2.40.0