Dear libtool gurus,
More and more GNU packages start using shared libraries. One example is
libintl (from the GNU gettext package), which installs itself as a shared
library by default now. It is used by many other packages, like textutils,
gcc, hello, and others, which don't use libtool.
For
I can see six possible approaches:
The 7th is to have the shared library use pkg-config, allowing other
tools to find out about it without relying on the linker configuration.
Its much cleaner than any of the other choices you mention, and
thankfully, has nothing to do with libtool (phew!)
--p
Bruno Haible [EMAIL PROTECTED] writes:
3) Introduce a libintl-config script that sets outputs the right -L and
-rpath option.
This may or may not help you if you're linking with *any* other tools
that are installed in /usr/lib and their foo-config scripts output
-L/usr/lib.
In that case
Rob Browning [EMAIL PROTECTED] wrote:
Bruno Haible [EMAIL PROTECTED] writes:
3) Introduce a libintl-config script that sets outputs the right -L and
-rpath option.
This may or may not help you if you're linking with *any* other tools
that are installed in /usr/lib and their foo-config
On Mon, Nov 19, 2001 at 11:15:37AM +0100, Lutz Müller wrote:
Hi Gary,
where should I ask for an lt_dlforeachfile function that actually scans
a directory when called a second time?
The libtool list [EMAIL PROTECTED] is the best place. However, I guess
I am not understanding your question
From: Bruno Haible [EMAIL PROTECTED]
Date: Mon, 19 Nov 2001 19:08:59 +0100 (CET)
1) We don't change our packages. We only tell the user that he should have
used LDFLAGS=-L${prefix}/lib -rpath ${prefix}/lib
6) Let each package search for 'libtool' in $PATH and use it if found,
Paul Eggert writes:
6) Let each package search for 'libtool' in $PATH and use it if found,
and fall back to 1) if not found
This works only when the same C compiler is used to build the package
as was used to configure libtool.
Can you please explain why (6) has this
pkg-config doesn't do that. its an almost impossible task unless you
Are you talking about some new tool that I had not previously heard
about or are you talking about a script like the
'/usr/local/bin/gnome-config' I see on my system?
its a replacement for *all* such scripts. its a C
Rob Browning [EMAIL PROTECTED] writes:
The problem I'm talking about is if Makefile.am's use
LDFLAGS = `gnome-config --libs foo` `foo-config --libs bar`
then if you've got a normal gnome-dev package installed, such that
it's libs are in /usr/lib, it will (or at least it used to) put
On 19 Nov 2001, Russ Allbery wrote:
Rob Browning [EMAIL PROTECTED] writes:
The problem I'm talking about is if Makefile.am's use
LDFLAGS = `gnome-config --libs foo` `foo-config --libs bar`
then if you've got a normal gnome-dev package installed, such that
it's libs are in
Bob Friesenhahn [EMAIL PROTECTED] writes:
How is the application developer to know which directories are searched
by default?
One can safely assume that /usr/lib and /usr/include are always searched
by default. Those are the only ones that I'd expect people to
automatically leave out of the
11 matches
Mail list logo
