On Sat, 2004-11-13 at 15:27 -0800, Jacob Meuser wrote:
> On Sat, Nov 13, 2004 at 10:21:19AM +0100, Ralf Corsepius wrote:
> > It's just that their functionality
> > intersects and partially conflicts.
>
> how?
>
> pkg-config is used to give basic information about installed packages.
> libtool is used to build libraries.
>
> pkg-config is used in configure scripts.
> libtool is used in Makefiles.
>
> yes, it's possible to use constructs like
>
> foo.so: foo.o
> ${CC} ${LDFLAGS} -o foo.so foo.o `pkg-config bar --libs`
>
> in Makefiles, but this is not overlap in a conflicting way.
>
This is actually exactly what happens when you use pkg-config in a
configure script. It generates a (e.g.) GLIB_LIBS Makefile variable and
you arrange for the contents of that to be added to the link line --
just like you say here.The conflict is that pkg-config not only provides the -L and -l needed to the library, but also those for all of its dependency libraries. So does Libtool. They're both trying to deal with platforms like Solaris that don't have a needed-following link loader. It would be far neater if they could co-operate with this. Scott -- Have you ever, ever felt like this? Had strange things happen? Are you going round the twist?
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Libtool mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/libtool
