From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-03-11 07:14:49
> > I've just comitted a quite small (textually), but important
> > change.
> Which causes trouble here :-)
Oops! Thanks for catching another bug.
I think that eventually, your test-case should become example or test in V2
tree. But why "eventully"? If you send the current version (just in case it's
different from the last you've send), I'll turn it into automated test.
You'd only need to specify copyright text to apply for all Jamfiles/sources.
> When trying to run
> bjam --v2 release/debug-symbols=on threading=multi stdlib=stlport
> on my last test-case (cd bjam/program first), _all_ object files are
> compiled _three_ times.
> All libs get linked twice, all exe's too.
In fact, some object files are compiled twice even with "bjam --v2". The
reason appeared simple: they are requested twice, with precisely the
same set of properties. The only problem is that properties are listed in
The cause is a bug deep inside V2 internals that nobody took time to fix...
Ok, after fixing it "bjam --v2" works ok and the command line you gave
produces reasonable results, too.
> bjam --v2 release/debug-symbols=on threading=multi
> results in the (unexpected) build path
> Why does bjam suddenly add optimization-off ?
I don't think it should. But I cannot reproduce the problem. Seems the test
case is indeed out of sync.
P.S. BTW, I think I've fixed the <dependency> issues you've raised. I'm about
to comit the changes soon.
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