Re: building 1.30.0 gcc static libraries

From: Gary Powell (powellg_at_[hidden])
Date: 2003-03-21 20:29:20

--- In jamboost_at_[hidden], David Abrahams <dave_at_b...> wrote:
> "Powell, Gary" <powellg_at_a...> writes:
> 
> > Hi,
> > What is the bjam control flag for making static vs shared 
libraries? 
> 
> There is none. Each library specifies individually whether it has
> shared and/or static products.
> 
> > I tried
> > bjam "-sBUILD=release/<instruction-set>pentiumpro<link>static"
> This is wrong------------------------------------^^^^^^^^^^^^
> 
> There is no <link> feature in Boost.Build v1, and even if there 
were,
> you'd need a slash.
Sorry I was confused by an earlier post that mentioned <link>static. 
I made the assumption that it worked like the <instruction-set> stuff.

> 
> > but it still made an .so (shared) library.
> 
> Which library were you building? I'm guessing Boost.Threads because
> it conspicuously doesn't have a static build on Windows (you can't 
do
> TLS without a DLL).
I'm using Linux and is that also true? 

But it's ok, as we are using some other thread management package. 
But I thought I also saw it for regex as well. The gcc.mak file for 
it has a link line of -shared. I did try and build it using -static 
and that worked but I am also wondering why we don't build both.

> 
> > And is it possible to build a debug version that doesn't use the
> > debug Stlport?
> > (I'm working on building the gcc-stlport version.)
> 
> Yes, you want to put <runtime-build>release in your BUILD 
properties:
> 
> -sBUILD=debug/<runtime-build>release/<instruction-
set>pentiumpro
> 
> HTH,
Thanks for the help.

-Gary-