1
1
<!--
2
- $Header: /cvsroot/pgsql/doc/src/sgml/dfunc.sgml,v 1.24 2003/03/25 16:15:35 petere Exp $
2
+ $Header: /cvsroot/pgsql/doc/src/sgml/dfunc.sgml,v 1.25 2003/04/10 01:22:44 petere Exp $
3
3
-->
4
4
5
5
<sect2 id="dfunc">
@@ -14,7 +14,8 @@ $Header: /cvsroot/pgsql/doc/src/sgml/dfunc.sgml,v 1.24 2003/03/25 16:15:35 peter
14
14
</para>
15
15
16
16
<para>
17
- For more information you should read the documentation of your
17
+ For information beyond what is contained in this section
18
+ you should read the documentation of your
18
19
operating system, in particular the manual pages for the C compiler,
19
20
<command>cc</command>, and the link editor, <command>ld</command>.
20
21
In addition, the <productname>PostgreSQL</productname> source code
@@ -47,13 +48,10 @@ $Header: /cvsroot/pgsql/doc/src/sgml/dfunc.sgml,v 1.24 2003/03/25 16:15:35 peter
47
48
here.
48
49
</para>
49
50
50
- <para>
51
-
52
51
<!--
53
- Note: Reading GNU Libtool sources is generally a good way of figuring out
54
- this information. The methods used within
55
- <productname>PostgreSQL</> source code are not
56
- necessarily ideal.
52
+ Note: Reading GNU Libtool sources is generally a good way of
53
+ figuring out this information. The methods used within PostgreSQL
54
+ source code are not necessarily ideal.
57
55
-->
58
56
59
57
<variablelist>
@@ -160,7 +158,7 @@ cc -shared -o foo.so foo.o
160
158
<indexterm><primary>MacOS X</></>
161
159
<listitem>
162
160
<para>
163
- Here is a sample . It assumes the developer tools are installed.
161
+ Here is an example . It assumes the developer tools are installed.
164
162
<programlisting>
165
163
cc -c foo.c
166
164
cc -bundle -flat_namespace -undefined suppress -o foo.so foo.o
@@ -271,17 +269,13 @@ gcc -shared -o foo.so foo.o
271
269
</varlistentry>
272
270
273
271
</variablelist>
274
- </para>
275
272
276
273
<tip>
277
274
<para>
278
- If you want to package your extension modules for wide distribution
279
- you should consider using <ulink
280
- url="http://www.gnu.org/software/libtool/"><productname>GNU
281
- Libtool</productname></ulink> for building shared libraries. It
282
- encapsulates the platform differences into a general and powerful
283
- interface. Serious packaging also requires considerations about
284
- library versioning, symbol resolution methods, and other issues.
275
+ If this is too complicated for you, you should consider using
276
+ <ulink url="http://www.gnu.org/software/libtool/"><productname>GNU
277
+ Libtool</productname></ulink>, which hides the platform differences
278
+ behind a uniform interface.
285
279
</para>
286
280
</tip>
287
281
0 commit comments