From: Reece Dunn (msclrhd_at_[hidden])
Date: 2004-07-05 04:52:34
Vladimir Prus wrote:
>Reece Dunn wrote:
> > This toolset requires the CVS version of BBv2 and follows the
> > of the latest CVS changes (NOTE: default-paths rule needs work to detect
> > the various CodeWarrior versions). This makes the cw toolset
> > consistent with the other tools:
> > using cw : 6.1 : "C:/Program Files/Metrowerks/CodeWarrior/Other
> > Metrowerks Tools/Command Line Tools/mwcc.exe" ;
>That's good! I have only one (mechanical) problem with your toolset. Some
>the lines appear to be wrapped in attachment, for example the first comment
> # (See accompanying file LICENSE_1_0.txt or copy at
>(Note there's no "#" on the second line). There are such wrappings in other
>places too. Maybe you can try resending?
I am reworking the toolset slightly. There are a few fixes I want to put in
place. I am also looking at enabling response files in version 7+. I have
now fixed the lines so they are under 80 characters and will post with the
Q: How do you create a spanned line in an action? Worst case: you will have
to manually correct those lines.
>Ah.. and the "TODO" at the top on the first is probably no longer
>since you require CVS version ;-)
I caught that one earlier, too! It was because the code was originally
written using the 1.31 BBv2 code.
BTW: I like the new CVS approach, compared to the 1.31 version :). However,
I agree with your other post that a common.join-command would be beneficial,
so I'll see what I can do. Also, how about either 1) a common.resolve-path
that appends ProgramFiles as a prefix; or 2) make that a part of
Also, it may also be useful to add a search in the Windows directory as well
to allow .NET toolsets to be written (the files are located in the Windows
Want to block unwanted pop-ups? Download the free MSN Toolbar now!
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