[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: how to make libtool link with static system libraries instead of dyn
|
From: |
Nick Bowler |
|
Subject: |
Re: how to make libtool link with static system libraries instead of dynamic |
|
Date: |
Fri, 6 Mar 2015 12:00:43 -0500 |
|
User-agent: |
Mutt/1.5.23 (2014-03-12) |
On 2015-03-06 16:35 +0000, Andy Falanga (afalanga) wrote:
> From: Peter Johansson [mailto:address@hidden
> Sent: Thursday, March 05, 2015 6:46 PM
[...]
> > On 03/06/2015 09:24 AM, Andy Falanga (afalanga) wrote:
> > > I am wondering how I would make libtool link with static versions of
> > already installed libraries instead of the dynamic ones. I have
> > something like this in Makefile.am
> > >
> > > pyexec_LTLIBRARIES = mylib.la
> > > mylib_la_LDFLAGS = -Wl,-Bstatic
> > > mylib_la_LIBADD = -lz -lrt -lboost_python ....
[...]
> > The -all-static option might be useful for you
>
> Thanks for the suggestion but it didn't produce what I need. It had the
> same effect as using "mylib_la_LDFLAGS = -static" which was to build only
> static versions, or archives, of the python module. This makes it so that
> the python interpreter cannot use the library: it must be shared.
It is not generally possible to link static archives into shared
libraries. The object files are usually incompatible.
Nevertheless, you should be able to force the issue by directly listing
archive filename(s) in _LIBADD, instead of using the -l option.
Regards,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)