Alexander Hansen wrote: [] > My understanding is that this would primarily be the case for builds > against static-only library packages. Unfortunately, since we've got > packages that install both static and dynamic libraries, scripting > rebuilds of every package that has a ".a" file would be a pretty big > rebuild on a typical user's system.
I must admit that I never understood the usefulness of the *.la files. As far as I can see, all libtool uses them for is to replace "-lfoo" on a "libtool --mode=link" line by the explicit filename of the library on the linker line, adding some dependencies at the same time - an exploit that is totally unnecessary. The linker understands perfectly well "-lfoo", whether it means a static or a dynamic library, and dependencies are usually also handled by other utilities. Can someone give an example where the existence of an *.la file is useful or perhaps even necessary? -- Martin ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
