logo       

FYI: mention libmumble++.a -> libmumble___a_SOURCES in doc.: msg#00005

sysutils.automake.patches

Subject: FYI: mention libmumble++.a -> libmumble___a_SOURCES in doc.

I'm checkin this in. This question seems to come up
periodically on the list.

Index: ChangeLog
from Alexandre Duret-Lutz <duret_g@xxxxxxxx>

* automake.texi (Canonicalization): The sources for libmumble++.a
go into libmumble___a_SOURCES.

Index: automake.texi
===================================================================
RCS file: /cvs/automake/automake/automake.texi,v
retrieving revision 1.270
diff -u -r1.270 automake.texi
--- automake.texi 18 Mar 2002 11:04:17 -0000 1.270
+++ automake.texi 9 Apr 2002 18:42:21 -0000
@@ -504,7 +504,9 @@

For example, if your program is named @code{sniff-glue}, the derived
variable name would be @code{sniff_glue_SOURCES}, not
-@code{sniff-glue_SOURCES}.
+@code{sniff-glue_SOURCES}. Similarly the sources for a library named
+@code{libmumble++.a} should be listed in the
+@code{libmumble___a_SOURCES} variable.

The strudel is an addition, to make the use of Autoconf substitutions in
macro names less obfuscating.
--
Alexandre Duret-Lutz





<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise