Re: [boost] bjam variants, subvariants and default build

From: rogeeff (rogeeff_at_[hidden])
Date: 2002-07-16 16:58:21

--- In jamboost_at_y..., Rene Rivera <grafik666_at_r...> wrote:
> >
> >lib my_lib : source.cpp
> > :
> > : <release><threading>multi
> > ;
> 
> Doesn't work, and is incorrect. AFAIK

What did you mean in docs then?

[[<compiler>]<variant>]<feature>value1[/value2...]

> Not implied by lib, nor dll. Only <shared-linkable>true is implied 
by dll.

How does it related to <target-type>?

> The global default is in the DEFAULT_BUILD variable. But changing 
that
> really does change it globally. Everything will then build with that
> default. So unless you are doing this in your own PRIVATE BUILD 
TREE don't
> do it. And especially don't do it in a toolset, I don't even know 
what the
> consequences would be.

Why? For if for given toolset I want to redefine global default build 
settings?

> 
> >4. unrelated question, but still, since you mention it once: how 
to get the
> preprocessor 
> >result with bjam?
> 
> Ahh, a really tricky question... I usually add a compiler specific
> requirement to the target I'm interested in like so for GCC:
> 
> exe fubar : fubar.cpp : <gcc><*><cflags>-E : ;

I was looking for some way to do this withour changing of Jamfile

Gennadiy.