From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-11-14 08:50:53
On Saturday 12 November 2005 01:48, Reece Dunn wrote:
> Zhon Johansen wrote:
> > After upgrading to the current version of Boost.build v2, my
> > <define>_DEBUG is no longer working.
> > I notice there is no -D_DEBUG in my cl.exe line. On the other hand I do
> > see /c.
> The <define> and <include> options are in a response file associated
> with the cpp file. Thus, if you have test.cpp, the response file will be
> in the build directory (e.g. bin/msvc-7.1/release/test.cpp.rsp).
> Are you getting any build problems due to _DEBUG not being defined?
> NOTE: You shouldn't need to specify _DEBUG as the debug/release settings
> should be taken care of by the variants, e.g.:
> $ bjam debug
> Volodya/Rene/Dave: Is there a reason why variant debug doesn't define
> _DEBUG, but variant release defines NDEBUG. VC projects define _DEBUG
> for release builds.
As for me, just because I never used or even knew about _DEBUG. I always used
NDEBUG for guard debug code. It does not seem that _DEBUG is as universal as
NDEBUG, do we really need to add it to "debug" variant? Maybe, only for msvc
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