Re: [jamboost] How to suppress particular target subvariant from building?

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-02-06 01:08:05

----- Original Message -----
From: "Rene Rivera" <grafik666_at_[hidden]>

> On 2002-02-06 at 02:35 AM, bmosher_at_[hidden]
> (bmosher_at_crosswinds_dot_net) wrote:
>
> >Hello all,
> >
> >[I don't check this email address very frequently, so please direct
> >any replies to the list only -- thanks.]
> >
> >One of the targets in my tree cannot be linked against the static
> >runtime library. Is there an easy way to suppress this
> >target/subvariant combination from building during those times that I
> >build the rest of the tree "<runtime-link>dynamic"?

This makes no sense to me. If the target can't be linked against the static
runtime, and you don't want to build it when you specify the dynamic
runtime, when /would/ you build it?

> >I tried a number of things to conditionally set <suppress> on the
> >target, but I couldn't determine a way to tell what the <runtime-
> >link> property was set to. I'm afraid I don't have a complete grasp
> >on the details of boost.build. I love the enhanced features that come
> >with it, unfortunately it seems quite a bit more complicated than the
> >stock jam/jambase. Any pointers here?
>
> There is no easy way (that I know) of knowing what the <runtime-link> is
set
> to unless you happen to be in the toolset. And even if you did something
in
> the toolset it would be too late to suppress the target. And doing it
anywhere
> else (with the flag* rule) would cause all kinds of other problems.
>
> When I wrote the <suppress> I wasn't thinking about the use that are
trying,
> but it seems usefull. I can see how one would like to change which targets
get
> built depending on the type of build they are doing.
>
> If, lets say, I changed the <suppress> so that one could specify a feature
> spec to indicate when to suppress. For example you could then specify it
this
> way:
>
> exe my-test : my_test.cpp : : debug release <suppress><runtime-link>static
;
>
> Does that convey what you are trying to do?

...and why wouldn't use just put <runtime-link>dynamic in the target
requirements?

I'm really confused about wher this is headed.

-Dave