From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-08-30 09:11:59
As pointed about by Stefan, at the moment the intel toolset won't work with
vc8 as backend, like shown at: http://tinyurl.com/oqrf7
VC8 does not have static multithreaded runtime, so if we try to request it, we
get link error.
We talked with Stefan over Jabber now, and there are some conclusions.
1. At the moment, intel install is bound to specific VC backend version, and
V2 does not allow to change that. That binding is done via .bat file, that
also include the /QvcNN option for the VC version.
2. V2's intel toolset has <compatibility> option that is translated
into /QvcMM option. At the same time Stefan says it does not make much sense
for V2 to pass different /QvcMM option than the VC backend version. And .bat
files already contain /Qvc option, so probably V2 should not pass any such
option at all.
3. At the same time, when using VC8 as backend, V2 should alter the flags
passed to compiler, to avoid requesting static single-threaded runtime.
One possible solution is this:
1. Declare that 'compatibility' parameter to intel-win.init is meat to specify
the version of backend that's configured. Maybe rename that parameter
2. Stop intel-win.jam from passing any /QvcNN options.
3. When backend version is 8.0, modify the compiler options to avoid link
Another alternative is that:
1. We require that prior to configuring intel, user configures some msvc
2. When configuring intel, user specifies the already-configured version of
3. Boost.Build arranges for the right /Qvc option to be passes to intel, and
will also call msvc's configure script for the choosen version.
This approach allows to test intel with two backed versions at the same time.
-- Vladimir Prus http://vladimir_prus.blogspot.com Boost.Build V2: http://boost.org/boost-build2
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