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

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-07-16 17:20:08

----- Original Message -----
From: "rogeeff" <rogeeff_at_[hidden]>
>
> What did you mean in docs then?
>
> [[<compiler>]<variant>]<feature>value1[/value2...]

I think that's a doc bug.

> > Not implied by lib, nor dll. Only <shared-linkable>true is implied
> by dll.
>
> How does it related to <target-type>?

<target-type> encodes the type of target being built. It's unrelated to
<runtime-link>, because in general you can link any kind of target to
either static or dynamic runtime libraries.

> > 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?

Because it wasn't designed to work that way, and probably won't work?

> > >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

I always just do bjam -n -a, copy the build command, change -c to -E, and
remove the -o.... stuff. Yeah, the build system should make this more
convenient.

-Dave