libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: TODO ... solution to the pkg-config "conflict"?


From: Jacob Meuser
Subject: Re: TODO ... solution to the pkg-config "conflict"?
Date: Sun, 14 Nov 2004 17:37:02 -0800
User-agent: Mutt/1.4.2i

On Sun, Nov 14, 2004 at 08:53:15AM +0000, Scott James Remnant wrote:
> On Fri, 2004-11-12 at 23:02 -0800, Jacob Meuser wrote:
> 
> > > It doesn't care about package versions, but it has to care about library
> > > versions and paths to libraries.
> > 
> > again, functionality provided by pkg-config.
> > 
> > I am contesting the claim "Libtool already has all the information
> > it needs".
> > 
> I actually tend to think we should look at this the other way ... if we
> could expose the information Libtool has to other tools, pkg-config
> could defer to Libtool.
> 
> So rather than libtool taking over pkg-config, we make them work
> together.

so, what you want, is simply something like ...

$ pkg-config --libs foo
-L/path/to -lfoo
$ pkg-config --libs-libtool foo
/path/to/libfoo.la
$ pkg-config --libs bar
-L/path/to -lbar -L/path/to -lfoo
$ pkg-config --libs-libtool bar
/path/to/libbar.la

where libbar depends on libfoo?

if so, then write the patch and give it to the pkg-config folks.
I can't imagine that you'd have the time to reimplement pkg-config,
but not the time to patch it.

-- 
<address@hidden>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]