Subject: Re: [Boost-build] <undef> property doesn't work?
From: Alexandre Koptelov (alexandre.koptelov_at_[hidden])
Date: 2008-10-02 16:04:44
After writing down the problem the best solution seems to be #undef'ing
_DEBUG right before #include'ing python stuff.
Still the problem of overriding properties stays as academic interest... =)
Alexandre Koptelov wrote:
> Vladimir Prus wrote:
>> On Thursday 02 October 2008 17:21:21 Alexandre Koptelov wrote:
>>> It seems that boost-build now doesn't support <undef> for any toolset
>>> except acc. Is there any reason for that?
>> Lack of demand, I think.
> Ok, I see.
> Then I suppose there's another way to override <define>s from global
> The Jamroot contains project definition with requirement (among other)
> `<variant>debug:<define>_DEBUG' that is inherited by all subprojects.
> One of them is a python extension. That extension is linked with release
> python library for both `release' and `debug' variants, so _DEBUG
> shouldn't be defined when it is compiled. How could it be done?
>> - Volodya
>> Unsubscribe & other changes:
> Unsubscribe & other changes:
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