From: John Maddock (john_at_[hidden])
Date: 2005-08-02 04:32:35
> They don't. When library targets are generate to variants directories,
> that name mangling scheme does not seem necessary -- it's all in the
> path already.
Oh shucks, so the question then is: if you did add <define>BOOST_ALL_NO_LIB
as a requirement to all bbv2 targets, how on earth do we verify that the
installed mangled names are correct? I repeat what I said before: this is a
common cause of bugs, so eyeball inspection of the names is not a solution.
If you can come up with some other kind of test (that can be run as part of
our regression tests) that would validate that the autolink and installed
names match then I'll be happy.
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