Re: [jamboost] Platform SDK toolset initialization

From: Andrey Melnikov (melnikov_at_[hidden])
Date: 2005-08-18 23:13:45

Alexey Pakhunov wrote:
> Alexey Pakhunov wrote:
> > Exactly. I'm working on msplatformsdk.jam and corresponding
> > modifications of msvc.jam (and other files). This version will
> 
> I've encountered one problem with Platform SDK toolset. 

IMO PSDK isn't a toolset. I think that your approach with integrating MS 
PSDK support into msvc toolset was ok. I only disliked that <mspsdk> 
feature was bound to Visual Studio.

Ultimately, I'd like to see the following:

- ms-platform-sdk.jam module declares psdk-related features and defines 
common rules;
- msvc.jam and other toolsets reuse ms-platform-sdk.jam code and contain 
toolset-specific psdk code;

The idea of ms-platform-sdk.jam is just to avoid code duplication. At 
the moment we are only working on MSVC, and no duplication will occur. 
For now we can still have all PSDK code in msvc.jam, but just have in 
mind the final picture and choose the right scope and names for the 
features we add.

> It seems PSDK 
> setup script 'SetEnv.cmd' tries to detect MS Visual Studio installation 
> and fails if nothing was found. When two VS installations are installed 
> only the latest will be detected and used.

Why do you think so? I looked at Windows Server 2003 SP1 SDK and 
SetEnv.cmd looks for %DevEnvDir% and %MSVCDir% first. vcvars32.bat from 
VC7.1 sets both, and vcvars32.bat from vc8 sets only %DevEnvDir%.

> So the two steps initialization that I tried to implement will not work 
> correctly:
> 
> actions compile.c bind RSP
> {
> ...\vcvars32.bat
> ...\setenv.cmd
> cl ...
> }
>
> The only solution that I see now is manually set PATH, INCLUDE and LIB 
> variables (or equivalents) instead of calling 'SetEnv.cmd'. Any other 
> ideas?

It seems that vcvars + setenv work when I try them manually. Why do you 
think they don't?

Andrey