Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
2e1cb733
G
Gpdb
项目概览
Greenplum
/
Gpdb
通知
7
Star
1
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
Gpdb
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
2e1cb733
编写于
10月 06, 2013
作者:
A
Andrew Dunstan
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Document support for VPATH builds of extensions.
Cédric Villemain and me.
上级
7db0dc0e
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
28 addition
and
1 deletion
+28
-1
doc/src/sgml/extend.sgml
doc/src/sgml/extend.sgml
+28
-1
未找到文件。
doc/src/sgml/extend.sgml
浏览文件 @
2e1cb733
...
@@ -935,7 +935,7 @@ include $(PGXS)
...
@@ -935,7 +935,7 @@ include $(PGXS)
To use the <acronym>PGXS</acronym> infrastructure for your extension,
To use the <acronym>PGXS</acronym> infrastructure for your extension,
you must write a simple makefile.
you must write a simple makefile.
In the makefile, you need to set some variables
In the makefile, you need to set some variables
and
finally
include the global <acronym>PGXS</acronym> makefile.
and include the global <acronym>PGXS</acronym> makefile.
Here is an example that builds an extension module named
Here is an example that builds an extension module named
<literal>isbn_issn</literal>, consisting of a shared library containing
<literal>isbn_issn</literal>, consisting of a shared library containing
some C code, an extension control file, a SQL script, and a documentation
some C code, an extension control file, a SQL script, and a documentation
...
@@ -1171,6 +1171,33 @@ include $(PGXS)
...
@@ -1171,6 +1171,33 @@ include $(PGXS)
</para>
</para>
</caution>
</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>
<para>
The scripts listed in the <varname>REGRESS</> variable are used for
The scripts listed in the <varname>REGRESS</> variable are used for
regression testing of your module, which can be invoked by <literal>make
regression testing of your module, which can be invoked by <literal>make
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录