|
Home > Archive > Debian Developers > July 2005 > *.la dependency_libs and -dev deps
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
*.la dependency_libs and -dev deps
|
|
| Loïc Minier 2005-07-31, 7:48 am |
| Hi,
I tried following the thread on libtool and -dev inter-dependencies,
and I'd like someone to confirm the way to go (a summary of the SUMMARY
thread would be nice  .
What I'm currently doing right now is adding -dev dependencies on -dev
packages for each "-l" in dependency_libs.
I'm currently not paying attention to "*.la" in dependency_libs.
Is that correct?
Bye,
--
Loïc Minier <lool@dooz.org>
Come, your destiny awaits!
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Steve Langasek 2005-07-31, 7:48 am |
| On Sun, Jul 31, 2005 at 12:55:51PM +0200, Loïc Minier wrote:
> I tried following the thread on libtool and -dev inter-dependencies,
> and I'd like someone to confirm the way to go (a summary of the SUMMARY
> thread would be nice .
> What I'm currently doing right now is adding -dev dependencies on -dev
> packages for each "-l" in dependency_libs.
> I'm currently not paying attention to "*.la" in dependency_libs.
> Is that correct?
No, it's backwards. If an application is linking against your library using
libtool, all of the .la files your own library references *must* be
available at build-time, even if doing dynamic linking. The packages
providing the "-l" libs are *not* required for normal operation, but they
are required if you intend to support static linking or linking with a
broken version of libtool.
--
Steve Langasek
postmodern programmer
|
|
|
|
|