Re: libtool wants to install LIBRARY.lai, but it doesn't exist

[Marc Singer]

On Thu, Mar 31, 2005 at 11:34:37PM +0100, Roger Leigh wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Ralf Wildenhues <address@hidden> writes:
> 
> > * Marc Singer wrote on Thu, Mar 31, 2005 at 10:59:13PM CEST:
> >> On Thu, Mar 31, 2005 at 10:20:12PM +0200, Ralf Wildenhues wrote:
> >> 
> >> > - .pc files come from pkgconfig.  While a seemingly easy tool and easy
> >> > solution, its incapable to solve some more complex problems.  (You seem
> >> > to have noted that already.)  pkgconfig has nothing to do with the
> >> > Autotools autoconf/automake/libtool except that by chance there might
> >> > now be some maintainer overlap and that there has been the idea of
> >> > absorbing its functionality into Libtool.
> >> 
> >> IMHO, what PC files do, the .la files can do better. 
> >
> > ACK.
> 
> In the library linking case, certainly.  But what about the CFLAGS for
> compiling client code, modversion, and the ability to embed other
> variables e.g. plugin directory paths?  Those aren't catered for at
> all by libtool .la files, and so if the two are to be merged, libtool
> should support these additional features.

I cannot speak to any specific case as I'm not involved in the work.
It should be clear, though, that the proliferation of redundant
information is undesirable.  Perhaps the two formats could be merged
s.t. we have a single build-helper file format.