From: Reece Dunn (msclrhd_at_[hidden])
Date: 2006-06-18 09:17:22
Roland Schwarz wrote:
> Sean Huang wrote:
> > For msvc, if you are running 32-bit windows, I believe you can simply
> > uncomment the using msvc line. The toolset names are also changed and have
> > versions in it. For example, for 8.0, do bjam --v2 msvc-8.0
> Thank you. This took me one step further.
> Does this mean I have to configure all compilers that I have installed
> on my system? And then later on the commandline choose which one to use
> in a specific build?
At the moment, yes.
> using msvc : 6.0 : C:/Program Files/Microsoft Visual
> Studio/VC98/Bin/cl.exe ;
> using msvc : 7.1 : C:/Program Files/Microsoft Visual Studio
> .NET2003/Vc7/bin/cl.exe ;
Note that if they are in the default locations, you can just have:
using msvc : 6.0 ;
using msvc : 7.1 ;
> And on the command line:
> bjam --v2 toolset=msvc version=6.0
> However this simply does not work :-(
> It is always taking 6.0, but is not able to do a compile anyways,
> complaining that cl is not a program.
> Any hints?
You need to either say (if I have this correct), the verbose:
bjam --v2 toolset=msvc toolset:version=6.0
Or, with V2 you can say this more simply as:
bjam --v2 msvc-6.0
Express yourself instantly with MSN Messenger! Download today it's FREE!
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