Re: [boost] building shared boost libraries

From: Steve M. Robbins (steven.robbins_at_[hidden])
Date: 2002-03-02 18:31:18

On Sat, Mar 02, 2002 at 06:26:35PM -0500, David Abrahams wrote:
> 
> ----- Original Message -----
> From: "Steve M. Robbins" <steven.robbins_at_[hidden]>
> To: <boost_at_[hidden]>
> Sent: Saturday, March 02, 2002 6:08 PM
> Subject: Re: [boost] building shared boost libraries
> 
> 
> > On Sat, Mar 02, 2002 at 05:00:41PM -0500, David Abrahams wrote:
> > >
> > > ----- Original Message -----
> > > From: "Rene Rivera" <grafik666_at_[hidden]>
> > > > Try $(<[1]:G=:D=).
> > >
> > > Grist is always gone by the time you get inside an action, so :G= is
> > > redundant.
> >
> > Thanks!  Using $(<[1]:D=) does what I want.
> >
> >
> > > > There is one problem with this solution... it will tag any library
> > > > created
> > > > regardless of wether it's in Boost or not. If you happen to use
> the
> > > > Boost.Build system for something other than Boost, which I do, the
> > > > above would
> > > > not be "a good thing".
> >
> > Good point.  However, I'm only interested in using jam to build boost.
> > The Debian packages install into /usr/lib and /usr/include, so nobody
> > need be using jam after that.
> 
> However, you're not the only one using these toolset files. We're not
> going to break them for people who [...]

Oh, granted.  I'm not proposing that Boost itself adopt any such
change.  I'll keep it in the Debian patch.

> > I have two new problems:
> >
> > 1. Static libs should NOT be built using -fPIC.
> 
> They should if they're being linked into a dynamic lib, shouldn't they?

I don't follow.  If you want to use libboost_python in another shared
lib, then you'd link with the libboost_python.so, no?

-S

-- 
by Rocket to the Moon,
by Airplane to the Rocket,
by Taxi to the Airport,
by Frontdoor to the Taxi,
by throwing back the blanket and laying down the legs ...
- They Might Be Giants