|
Boost-Build : |
From: Rene Rivera (grafik666_at_[hidden])
Date: 2002-02-06 00:07:56
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"?
>
>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?
-- grafik - Don't Assume Anything
-- rrivera_at_[hidden] - grafik_at_[hidden]
-- 102708583_at_icq - Grafik666_at_AIM - Grafik_at_[hidden]
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk