Alexandre Oliva wrote:
> On Apr 21, 2001, Eric Lemings <[EMAIL PROTECTED]> wrote:
>
> > 2.0 spawned a separate tool called pkg-config that allows all packages
> > to use one tool rather than several different scripts to query compile
> > flags, link flags, and other configuration data.
>
> What I don't understand is how pkg-config is going to find the
> configuration info of the various packages. I hope it's not going to
> require having them all installed in the same prefix.
No, it doesn't require that they all be installed with the same prefix; it
simply keeps its data files all in one location.
> One of the
> beauties of the *-config scripts is that all one had to tweak to get
> them to work and get the respective libraries found is the PATH (or a
> directory containing links).
It works the same more or less. New Autoconf macros that use pkg-config
look for it in the current path and it looks for data on installed
libraries in its data directory.
Eric.
_______________________________________________
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool