From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-10-22 15:24:19
On Sunday 22 October 2006 22:09, Rene Rivera wrote:
> Vladimir Prus wrote:
> > On Sunday 22 October 2006 19:43, Rene Rivera wrote:
> >> * V1 does not have any special logic for figuring out if a toolset has
> >> or doesn't a debug runtime. And hence sets the "g" unconditionally when
> >> <runtime-build>debug is present.
> > Hmm, my experiments don't confirm this. I go to libs/thread/build and
> > run:
> > bjam -sBUILD="debug <runtime-build>debug"
> > the libraries created are:
> > libboost_thread-gcc-mt-d-1_35.a
> > libboost_thread-gcc-mt-d-1_35.so
> > libboost_thread-gcc-mt-d-1_35.so.1.35.0
> > And there's no 'g' in the library name. So it looks like some code
> > figured out that <runtime-build>debug does not affect gcc?
> After investigating for an hour what I can figure out is that a feature
> is not included in the build when that feature is not handled by the
> toolset. That is if the toolset doesn't specify a "flags <toolset> X
> <runtime-build>debug : -x ;" the runtime-build feature will not show up
> to the name tagging rule, or any place else AFAICT. Hence for many V1
> toolsets the "g" doesn't show.
Thanks, I think I know everything now. I'll either implement the similar
behaviour in V2 right away, or work around and implement the right behaviour
a bit later ;-)
> >> * The Boost V1 Jamfile builds all the variants resulting from
> >> specifying: "debug release [debug-python] <runtime-link>static/dynamic
> >> <threading>single/multi" on Windows (regardless of toolset). And
> >> otherwise from: "debug release [debug-python] <threading>single/multi".
> > So, on Windows only, we also add variation on <runtime-link> property.
> > Right?
> Yes. But I don't think that's the correct thing to do, i.e. it was a
That's probably only changeable for 1.35 ;-) For 1.34 we better have exactly
the same behaviour in V2 as now in V1. How about the attached patch?
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