docs patch
Adriaan de Groot <adridg-FlD2LfDziEhmR6Xm/[email protected]>
| Newsgroups | gmane.comp.tools.aap.devel |
|---|---|
| Message-ID | <[email protected]> |
a typo snuck into bram's fix of my previous docs addition, and i just
discovered {objecttype}, so i want to add a paragraph about it, too.
doc.diff
(text/x-diff, 1.7 KB)
Index: doc/user-depend.sgml
===================================================================
RCS file: /cvsroot/a-a-p/Exec/doc/user-depend.sgml,v
retrieving revision 1.26
diff -u -3 -p -r1.26 user-depend.sgml
--- doc/user-depend.sgml 28 Oct 2003 12:18:52 -0000 1.26
+++ doc/user-depend.sgml 29 Oct 2003 23:31:49 -0000
@@ -211,7 +211,7 @@ alternative build command to build the p
<bridgehead>Attributes for the Production Commands</bridgehead>
<para>
-The production commands understand wide variety of attributes.
+The production commands understand a wide variety of attributes.
Let us return to the generic form
of a production command:
<programlisting>
@@ -249,10 +249,30 @@ libtool libraries, not programs.
</note>
<warning>
-It is a bad idea (excepting ltprograms) to add targets
+It is a bad idea (excepting ltprograms, which belong
+in INSTALL_LTLIB) to add targets
to the wrong install variable, since the install
action that gets called for it will be wrong then as well.
</warning>
+
+<para>
+A slightly less-used command-attribute is
+<literal>objecttype</literal>, which changes
+the object file type from the default,
+(<literal>dllobject</literal>, for instance,
+for shared libraries), to something else.
+For programs that need to be linked by libtool,
+you may also want to force the object files used in the
+program to be compiled with libtool, since mixing
+non-libtool objects and libtool libraries can
+cause problems.
+For this, use the <literal>{ objecttype = ltobject }</literal>
+as well, so that libtool programs will usually
+have build commands like:
+<programlisting>
+:program { filetype = ltprogram } { objecttype = ltobject } ...
+</programlisting>
+</para>
<para>