Add words about shared libs on OS X.

CLUSTER_UNTESTED

1 files changed, 14 insertions, 0 deletions

diff --git a/gs/doc/Make.htm b/gs/doc/Make.htm
index fe5b550a2..c926c5d90 100644
--- a/gs/doc/Make.htm
+++ b/gs/doc/Make.htm
@@ -1548,7 +1548,9 @@ and <tt>x86_64</tt> binaries in one file, using the <tt>Makefile</tt>
 from <tt>configure</tt>. This can be achieved by using the following invokation of
 <tt>configure</tt>
 <blockquote>
+<code>
 ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc" CPP="gcc -E"
+</code>
 </blockquote>
 <p>
 You can choose the combination of valid architectures (i386/x86_64/ppc) that you
@@ -1558,6 +1560,18 @@ The separate options for <tt>CC</tt> and <tt>CPP</tt> are required because some
 the features used by <tt>configure</tt> to explore the capabilities of the preprocessor
 are not compatible with having multiple <tt>-arch</tt> options.
 <p>
+Building a shared library on MacOS X is the same as for other Unix-like systems, the
+"configure" step is done normally, and the "so" target is given to the make invocation,
+thus:
+<blockquote>
+<code>
+make so
+</code>
+</blockquote>
+The only difference compared to other Unix-like systems is that on OS X the resulting
+shared library is created with the ".dylib" file name extension, instead of the more
+usual ".so".
+<p>
 Finally, there is a <tt>macos-mcp.mak</tt> makefile that can be
 used to set up the Codewarrior shared library component build described
 in the section on <a href="#MacOS">Classic MacOS</a> above.