From: David Abrahams (dave_at_[hidden])
Date: 2003-08-26 18:37:43
Ross Smith <rosss_at_[hidden]> writes:
> David Abrahams wrote:
>> "Neal D. Becker" <nbecker_at_[hidden]> writes:
>>> You mean I can't just run bjam with no options and get the libs
>>> built with thread support? I need to add a command-line option?
>> The libraries that require thread support will be built with thread
>> support. The others will not, unless <threading>multi has been placed
>> in their default-build settings; <threading>single is the global
> Which leads to three questions:
> (1) How do we do this?
Do what? Get all multithreaded libraries automatically with zero user
intervention on the command-line? You convince the Boost developers
who told me single-threading should be the default when I started
Boost.Build that they were wrong, and I change the default.
> (2) Why isn't it documented? Are users supposed to know about this bit
> of voodoo by clairvoyance, or what?
> (3) How many other undocumented gotchas like this are lurking in there?
63 and a half.
-- Dave Abrahams Boost Consulting www.boost-consulting.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk