Boost logo

Boost-Build :

From: Stefan Slapeta (stefan_at_[hidden])
Date: 2006-08-30 10:09:54

Vladimir Prus wrote:
> 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.

Actually this is stored in a cfg file at compiler site. There are two
files where the choice taken at installation time is written hardcoded
into files:
- icl.cfg (compiler option /QvcNN)
- iclvars.bat (calls the vc version-specific vcvars32.bat)

> Another alternative is that:
> 1. We require that prior to configuring intel, user configures some msvc
> version.

That's not easily possible because you would have to change the files
above. So I wouldn't prefer this option.

> This approach allows to test intel with two backed versions at the same time.

To achieve this, another solution is possible that has my vote (but it
maybe has side effects):

Don't call iclvars.bat before invoking the compiler

Call the right vcvars32.bat based on the value of 'compatibility'. Set
additional intel paths (this would be easy).

This would allow bjam to control the back end actively (in case you
specified 'compatibility').

Downside: this could clash with environment settings for INCLUDE and LIB
  that have been set before. However, these clashes can never be avoided
totally anyway. Thinking loudly: is it desirable that bjam *resets*
these environment settings (INCLUDE/LIB) before setting its own?


Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at