From: David Abrahams (dave_at_[hidden])
Date: 2004-06-16 05:08:23
Vladimir Prus <ghost_at_[hidden]> writes:
> Mark Elston wrote:
>> I *had* read this but didn't get the significance. I'm not sure
>> I still make the connection.
>> Are you saying that the choice of compiler is now just another
>> feature? And these features can be combined with all other
>> features? So now I can do this:
>> bjam debug gcc MyTarget msvc release
>> to build debug and release versions of MyTarget using both gcc
>> and msvc compilers (not that I would do it this way...). Is this
> Yes, exactly. Above, "debug" is shortcut for <variant>debug and "gcc" is
> shortcut for <toolset>gcc, where both <variant> and <toolset> are features.
>> If so, I think I prefer the old way since it was actually somewhat
>> clearer about what was happening.
> That's the case where opinions differ, I'm afraid. It's hard to change this
> behaviour now, since V2 exists for quite some time and V2 users are
> accustomed to new behaviour.
Well, the shortcuts are optional. You can also write
bjam variant=debug toolset=gcc toolset=msvc variant=release MyTarget
>> BTW, I don't see anything in that section regarding compiler choice
>> or that this has become a generic feature. Having read all the
>> documentation I could get my hands on - including the stuff in
>> jam_src which I thought would still be accurate - I couldn't tell
>> that this had changed.
jam_src doesn't document anything having to do with toolsets or the
build system per-se other than the lowest-level operation of the jam
-- Dave Abrahams Boost Consulting http://www.boost-consulting.com
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