bug-automake
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: -module needs to be in Makefile.am?


From: Alexandre Duret-Lutz
Subject: Re: -module needs to be in Makefile.am?
Date: Wed, 10 Nov 2004 00:39:16 +0100
User-agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux)

>>> "Chris" == Chris Ison <address@hidden> writes:

 Chris> While trying to fix warnings produced during a bootstrap
 Chris> of a project, I found that we already had the -module in
 Chris> LDFLAGS within [configure.ac]. but it seems Automake wants
 Chris> the flag in Makefile.am.

Yes.

I'm installing this on HEAD and branch-1-9.

2004-11-10  Alexandre Duret-Lutz  <address@hidden>

        * doc/automake.texi (Libtool Modules): Make clearer that -module
        should appear explicitly in _LDFLAGS.

Index: doc/automake.texi
===================================================================
RCS file: /cvs/automake/automake/doc/automake.texi,v
retrieving revision 1.44.2.17
diff -u -r1.44.2.17 automake.texi
--- doc/automake.texi   1 Nov 2004 09:55:47 -0000       1.44.2.17
+++ doc/automake.texi   9 Nov 2004 23:36:37 -0000
@@ -3262,12 +3262,22 @@
 mymodule_la_LDFLAGS = -module
 @end example
 
-Ordinarily, Automake requires that a Library's name starts with
+Ordinarily, Automake requires that a library's name starts with
 @samp{lib}.  However, when building a dynamically loadable module you
-might wish to use a "nonstandard" name.
+might wish to use a "nonstandard" name.  Automake will not complain
+about such nonstandard name if it knows the library being built is a
+libtool module, i.e., if @samp{-module} explicitly appears in the
+library's @code{_LDFLAGS} variable (or in the common @code{AM_LDFLAGS}
+variable when no per-library @code{_LDFLAGS} variable is defined).
+
+As always, @code{AC_SUBST} variables are black boxes to Automake since
+their values are not yet known when @command{automake} is run.
+Therefore if @code{-module} is set via such a variable, Automake
+cannot notice it and will proceed as if the library was an ordinary
+libtool library, with strict naming.
 
-If @samp{mymodule_la_SOURCES} is not specified, then it defaults to the single
-file @file{mymodule.c} (@pxref{Default _SOURCES}).
+If @samp{mymodule_la_SOURCES} is not specified, then it defaults to
+the single file @file{mymodule.c} (@pxref{Default _SOURCES}).
 
 @node Libtool Flags
 @subsection _LIBADD and _LDFLAGS
-- 
Alexandre Duret-Lutz





reply via email to

[Prev in Thread] Current Thread [Next in Thread]