From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-10-13 00:17:17
> I'm using Boost.Build V2 (Milestone 7) Boost.Jam 03.01.07.
> Somehow, the command-line setting doesn't get through - I'll investigate
> that as soon as I have some spare time. In the meantime, I'd be grateful if
> someone can give me an idea of why this happens...
I think this might be because command line and environmental variables are
imported into global module in V2, and when executing actions those settings
are not visible. Alas, I'm not likely to look into this for a couple of days.
If you're interested in trying a quick workaround, add
JAMSHELL on $(targets) = [ modules.peek : JAMSHELL ] ;
right to the top of 'set-target-variables' rule in "new/toolset.jam". This
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