Do you mean by "self-contained" that it should even contain the C library
functions it uses?
If so, the only way I know of doing it is to make a static library
archive, and link it into a shared library, statically linking the C
library into it.
I don't think Libtool knows how to do this, thou
On Fri, 14 Mar 2003, Philip Willoughby wrote:
> Today, Ronald Landheer-Cieslak wrote:
> >Do you mean by "self-contained" that it should even contain the C
> >library functions it uses?
> >
> >If so, the only way I know of doing it is to make a static library
7;t
use the .a file produced by Libtool without prejudice.
rlc
On Fri, 14 Mar 2003, Ricardo Fabbri wrote:
> On Fri, 14 Mar 2003, Ronald Landheer-Cieslak wrote:
>
> > Do you mean by "self-contained" that it should even contain the C library
> > functions it uses?
>
On Fri, 14 Mar 2003, Philip Willoughby wrote:
> Today, Ricardo Fabbri wrote:
>> On Fri, 14 Mar 2003, Ronald Landheer-Cieslak wrote:
>>> Do you mean by "self-contained" that it should even contain the C
>>> library functions it uses?
>> I don't want
Hello all,
I am looking for a way to portably tell libtool to link in all objects of
a given static library. Basically, my problem is this:
I have an object file containing "constructor" and "destructor"
functions, which are not called from any program using my library, but
which are run autom
On Wed, 28 May 2003, Howard Chu wrote:
> > Ronald Landheer-Cieslak wrote:
> > I am looking for a way to portably tell libtool to link in all objects
> > of a given static library.
[snip]
> Link all of the static archive members into a single object file. This wor
d of platform).
I don't want to nag, but I don't quite see how the "don't link shared libs
to static libs" argument comes into play.
rlc
> Ronald Landheer-Cieslak wrote:
> >
> > Hello all,
> >
> > I am looking for a way to portably te
