From: Alan W. Irwin <irwin@be...> - 2004-02-17 01:36:29
I now know what is required for the libgd case where a variety of dependent
libraries may be necessary depending on the platform. If libgd.la is present
(meaning libtool collected dependency information) we want to allow libtool
to use that information rather than imposing our ideas about what the
dependent libraries are.
I have traced through the automake/libtool logic and looked at the parallel
case of libfreetype.la, and satisfied myself that when libgd.la is present
all we have to do is set
GDLIBCMD = -L/path/to/libgd -lgd
with the -L option dropped when the library location is default.
Of course the fallback when libgd.la is not present is to use our present
system which is
GDLIBCMD = -L/path/to/libgd -L/path/to/libpng -L/path/to/libjpeg \
-L/path/to/libz -lgd -lpng -ljpeg -lz
with the -L options almagamated if the same and dropped if default. This
should work in old cases, but I don't want all this unnecessary and
misleading (in the sense that more libraries than just libpng, libjpeg, and
libz are often required for the latest libgd) extra cruft in the link line
when libgd.la is present.
I have just committed changes to sysloc.in to make this idea work.
Rafael, will you please do the equivalent change for your new configuration
system when you get the chance?
Alan W. Irwin
Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).
Programming affiliations with the PLplot scientific plotting software
package (plplot.org), the Yorick front-end to PLplot (yplot.sf.net), the
Loads of Linux Links project (loll.sf.net), and the Linux Brochure Project