On Sun, 14 Nov 2004, Gary V. Vaughan wrote:
Hi Bob!
Bob Friesenhahn wrote:You seem to be a victim of a package install where every package has used its own unique installation prefix. It seems to me that most systems use just one or two installation prefixes.
Absolutely.
But the point is that pkg-config is supposed to help with parallel installs, and it most certainly does not!
It can help if the packages themselves are designed to support parallel installs by using versioned lib, include, share, etc., directories. That allows them to use the same installation prefix.
Libtool helps, but its resulting configuration (saved in .la files) is static, while pkgconfig's configuration is dynamic since it may be altered by the user.
You mean that the installed .pc files need to be altered by the user to give things a hope of linking? ;-)
But seriously, why would you install a .pc using library, and then alter the installed .pc file?
The libraries may be moved to (or reside in) a different location than when they were built. As you pointed out, pkg-config pulls configuration at run-time for each package, and the user has the ability to specify the pkg-config directory via PKG_CONFIG_PATH. This means that pkg-config is more end-user "tweakable" than libtool.
Libtool's .la file scheme expects more path stability than pkg-config does.
Bob ====================================== Bob Friesenhahn [EMAIL PROTECTED] http://www.simplesystems.org/users/bfriesen
_______________________________________________ Libtool mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/libtool
