On Tue, 1 May 2007, Richard Lemieux wrote:
Can anyone point me to a document explaining the general architecture of
'libtool', where it stores information, and where it takes information from,
and how it interacts with 'pkg-config'?
Libtool does not interface with 'pkg-config' at all. Applica
Hi,
This is a question about how libtool finds the libraries in a script.
The question arosed in the situation where I was compiling
'gphoto2' for an installation is a separate directory
'/rlxb4/opt/gphoto2' while there was already an older version of 'gphoto2'
installed in '/usr/local'.
I got t
> -Original Message-
> From: Havoc Pennington [mailto:[EMAIL PROTECTED]]
> Sent: Monday, April 23, 2001 6:36 PM
> To: Bernard Dautrevaux
> Cc: Alexandre Oliva; Eric Lemings; [EMAIL PROTECTED];
> [EMAIL PROTECTED]
> Subject: Re: Libtool and Pkg-Config
>
>
>
On Apr 22, 2001, Martijn van Beers <[EMAIL PROTECTED]> wrote:
> Maybe you should actually take a look at pkg-config instead of listening
> to people talking about it inaccurately.
Err... Perhaps if I had been pointed at it, instead of having had the
impression it was some tool in an early desig
Bernard Dautrevaux <[EMAIL PROTECTED]> writes:
> A necessary (and sufficient AFAICT) condition would be that, given the fact
> that libtool remember library dependencies, one use a tsort-like tool to
> topologically sort all the libraries, while detecting loops in the
> dependencies, and emitti
> -Original Message-
> From: Havoc Pennington [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, April 22, 2001 4:46 PM
> To: Alexandre Oliva
> Cc: Eric Lemings; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Libtool and Pkg-Config
>
>
>
> Alexandre Ol
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 th
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 shoul
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
Alexandre Oliva <[EMAIL PROTECTED]> writes:
>
> You wouldn't. This is totally out of the scope of libtool. Libtool
> is about linking with libraries, not compiling source files so that
> they can be linked with them. Not that it couldn't be extended so as
> to record user-directed flags at th
[EMAIL PROTECTED] writes:
> Ick! If anything, pkg-config should use libtool. I don't think libtool
> should *depend* on pkg-config at all. Libtool might be enhanced to
> help pkg-config get at certain data but I hope it does no more than
> that. That said, *.la files are already easy to parse.
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, ever
> install anything ou
On Apr 22, 2001, Eric Lemings <[EMAIL PROTECTED]> wrote:
> Exactly. So how would you get the compiler flags into libtool?
You wouldn't. This is totally out of the scope of libtool. Libtool
is about linking with libraries, not compiling source files so that
they can be linked with them. Not t
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, i
On Apr 22, 2001, Havoc Pennington <[EMAIL PROTECTED]> wrote:
> There's a PKG_CONFIG_PATH that controls where pkg-config looks for the
> data files. So now you don't actually have to do PATH, just
> PKG_CONFIG_PATH.
Phew! Good :-)
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.
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, ever
install anything outside the --prefix/--exec-prefix/--*dir specified
by the user. Having st
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
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 register their own data into p
Havoc Pennington wrote:
I think for libtool it's as simple as having a concept
of a "package"
in addition to a concept of a library, so we can pass "gtk+-2.0" to
libtool instead of "-L/home/hp/unst/lib -L/usr/X11R6/lib -lgtk-x11-1.3
-lgdk-x11-1.3 -lXext -lgdk_pixbuf-1.3 -lm -lpangox -lX11 -lpango
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 goi
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 configur
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.
>
>
[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 c
Alexandre Oliva <[EMAIL PROTECTED]> writes:
> On Apr 21, 2001, Havoc Pennington <[EMAIL PROTECTED]> wrote:
>
> > This would also help handle -R on Solaris and stuff like that.
>
> If it could handle a list of packages at once, yes, it would probably
> help on other systems such as DU too. But
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
On Apr 21, 2001, Havoc Pennington <[EMAIL PROTECTED]> wrote:
> This would also help handle -R on Solaris and stuff like that.
If it could handle a list of packages at once, yes, it would probably
help on other systems such as DU too. But the main problem with DU is
that -rpath flags override pr
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
"Gary V. Vaughan" wrote:
> Yes, I have been thinking about this. Although I was planning on writing a
> macro for autoconf-2.50 which would help generate the foo-config scripts. I
> think your idea is a much better approach, and I'll add it to the TODO list
> presently. Thanks.
You mean I act
Hi,
I'm all for it, but someone has to do the work. ;-)
This would also help handle -R on Solaris and stuff like that.
Havoc
___
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool
Hi Eric,
On Saturday 21 April 2001 6:12 pm, Eric Lemings wrote:
> Because of a growing number of config scripts for packages in GNOME 1.2
> (e.g. glib-config, xml-config, orbit-config. etc), development of GNOME
> 2.0 spawned a separate tool called pkg-config that allows all packages
> to use on
Because of a growing number of config scripts for packages in GNOME 1.2
(e.g. glib-config, xml-config, orbit-config. etc), development of GNOME
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
31 matches
Mail list logo
