On Mon, Oct 02, 2006 at 09:00:36PM +0200, Kurt Roeckx wrote:
> On Mon, Oct 02, 2006 at 01:51:58PM +0200, Axel Thimm wrote:
> > Can this be somehow dealt with within libtool? It would need to fork
> > the semantics of dependency_libs into static vs shared libs or
> > something similar. I guess the d
Hi,
On Mon, Oct 02, 2006 at 09:00:36PM +0200, Kurt Roeckx wrote:
> On Mon, Oct 02, 2006 at 01:51:58PM +0200, Axel Thimm wrote:
> > dependency_libs contains the linker switches/arguments that this
> > library was built with including the dependent libs, both directly
> > references as well as indir
On Mon, Oct 02, 2006 at 01:51:58PM +0200, Axel Thimm wrote:
> Hi,
>
> dependency_libs contains the linker switches/arguments that this
> library was built with including the dependent libs, both directly
> references as well as indirectly references through intermediate libs.
>
> For static linki
How annoying. I didn't test the example tarball and of course
didn't notice two files missing until after I hit 'send'.
I also added a -ldl for good measure, it wasn't needed on
my test platform.
Here's an updated example. Sorry for the inconvenience.
Cheers,
Peter
example.tar.gz
Description: a
Hello!
(For the record, I think what I'm trying to achieve can be
solved with libltdl, but I do not wish to use libltdl for
licensing reasons. I have complete understanding with not
getting any sympathy for that decision. I'm just asking
if there is a way out of my linking troubles...)
In a p
Hi,
dependency_libs contains the linker switches/arguments that this
library was built with including the dependent libs, both directly
references as well as indirectly references through intermediate libs.
For static linking one needs the whole dependency_libs information,
but for building again
