Alexandre Oliva [EMAIL PROTECTED] writes:
On Apr 22, 2001, Havoc Pennington [EMAIL PROTECTED] wrote:
pkg-config has some intelligence, i.e. if you request two libs at once
it will nuke duplicate flags and order the -l flags properly.
Err... It won't always remove duplicate -l flags,
Martijn van Beers wrote:
On Sun, Apr 22, 2001 at 07:34:42AM -0300, Alexandre Oliva wrote:
On Apr 22, 2001, Eric Lemings [EMAIL PROTECTED] wrote:
Currently, they just install their .pc file into pkg-config's data directory.
Which is exactly the wrong approach. A package should never,
On Sun, Apr 22, 2001 at 07:54:30AM -0300, Alexandre Oliva wrote:
On Apr 22, 2001, [EMAIL PROTECTED] wrote:
Patch below to override the fgrep test for IRIX 6.x, Solaris 2.x,
and Tru64 UNIX 4.x, 5.x.
It should at least retain the original behavior on other platforms.
And you shouldn't
Eric Lemings [EMAIL PROTECTED] writes:
Well I for one was unaware of the PKG_CONFIG_PATH variable. If that is true
however, how are client packages supposed to know where their .pc files are
supposed to be installed if this variable can be changed? Right now, I think most
assume that its
On Saturday 21 April 2001 9:36 pm, Matthew Schalit wrote:
Hi Gary, I gave your patch a try and it didn't work correctly in the
end, which was odd. I looked at configure, and the patch was corrupted.
The square brackets were missing:
My bad. Since libtool.m4 is processed by m4, one level of
On Saturday 21 April 2001 10:02 pm, Matthew Schalit wrote:
The only other thing I noticed was this section in libltdl/configure:
---
echo "$as_me:7795: checking whether deplibs are loaded by dlopen" 5
echo $ECHO_N
On Saturday 21 April 2001 11:20 pm, Peter Eisentraut wrote:
Gary V. Vaughan writes:
Failing major disasters, or the discovery of a showstopper, there are
less than 18 hours to go before the release of libtool-1.4 from CVS HEAD.
I think that's going to be a problem for you:
libtool$ make
Eric Lemings wrote:
What I do know though is that a few (if not several) packages are already using
pkg-config. So if libtool is extended with that functionality, it should be
compatible with the current behavior of pkg-config. This means that libtool
would first look for the .pc files and
[EMAIL PROTECTED] wrote:
On Sun, Apr 22, 2001 at 01:29:23AM -0600, Eric Lemings wrote:
I was thinking that if the data maintained by pkg-config could somehow be
added to the .la files and libtool could keep track (a registry perhaps) of
installed .la files, that would just about cover
On Sun, Apr 22, 2001 at 01:29:23AM -0600, Eric Lemings wrote:
Alexandre Oliva wrote:
I could do it with the current scheme, and tweaking PATH
is all it takes for me to choose which one a certain package will
find. I don't see how you'd accomplish that with a single pkg-config.
I'll
Alexandre Oliva [EMAIL PROTECTED] writes:
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.
Alexandre Oliva wrote:
On Apr 22, 2001, Eric Lemings [EMAIL PROTECTED] wrote:
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.
And how are packages going to
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
Gary V. Vaughan wrote:
Hi everyone,
$ ./configure
...
Configuring libtool 1.3e (1.900 2001/04/20 20:55:18)
...
checking host system type... i686-pc-linux-gnu
This is an a.out
On Apr 22, 2001, Havoc Pennington [EMAIL PROTECTED] wrote:
pkg-config has some intelligence, i.e. if you request two libs at once
it will nuke duplicate flags and order the -l flags properly.
Err... It won't always remove duplicate -l flags, will it? This
isn't always correct.
Also, it
On Apr 22, 2001, [EMAIL PROTECTED] wrote:
Patch below to override the fgrep test for IRIX 6.x, Solaris 2.x,
and Tru64 UNIX 4.x, 5.x.
It should at least retain the original behavior on other platforms.
And you shouldn't assume host == build, which you seem to do by
invoking host-specific
16 matches
Mail list logo
