Re: Platform SDK toolset initialization

From: Alexey Pakhunov (alexeypa_at_[hidden])
Date: 2005-08-19 08:36:06

Andrey Melnikov wrote:

> Don't call ms-platform-sdk.jam "a toolset" then. I wonder what is the 
> correct term for it? 

OK. :)

> A module?

stlport.jam refers to self as "stlport". We can do the same.

> environment ourselves if setenv.bat still . The problem is that the 
> environment must be set after calling vcvars32:

Yes.

> Fortunately it's possible with current $(prefix) framework.

Yes.

> - Should we set PATH for PSDK?

Yes, in order to allow amd64 and ia64 configurations for msvc-7.1 and below.

> - Should we call vcvars32?

I guess so.

> - Does vcvars32 offer us any advantages over setting the INCLUDE, LIB 
> and PATH manually even for Studio itself?

In the one hand it works now. BBv2 already supports 4 (even 5) versions 
of msvc and will support more. It is not a good idea to re-implement all 
of them.

In the other hand msplatformsdk currently supports only one version. 
Sure it will support future releases but it will be relatively easy to 
add required changes (if any).

> - Do we really need to set the evironment? Would adding -I $(STDHDRS) 
> option be better? Just like we do for Borland toolset?

It is more flexible from BBv2 point of view. The main problem is to 
re-implement and test new implementation. It is too much effort for nothing.

Best regards/Venlig hilsen,
Alexey Pakhunov.