Re: [BBv2] [msvc] amd64, ia64 and some other features

From: Alexey Pakhunov (alexeypa_at_[hidden])
Date: 2005-08-01 02:59:48

Andrey Melnikov wrote:

> - Recently I submitted my own bugfix-only patch (now including CVS diff) 
> which fixes some bugs in the toolset. 

Your changes are included into this patch.

> Or to wait until first patch is 
> reviewed and incorporated, and then change the next patch properly. I 
> don't know which way is better.

My patch can be submitted to CVS not sooner than M11 will be released. 
So I merge the fixes that will be checked in.

> - new feature names and values will need to be carefully selected and 
> pass a review in order to get accepted. See my discussion about 
> precompiled headers http://article.gmane.org/gmane.comp.lib.boost.build/9602

Agree.

>>'<toolset-sdk>psdk' makes the toolset use Platform SDK headers,
>>libraries and (for 64bit only) compiler.
> SDK is too generic. toolset-mspsdk would be better.

OK.

> I think we should reverse engineer the PSDK setvar.cmd switches and 
> check. I think that "platform" switch just #defines WINVER or something 
> like this. So built-in compiler should support it too.

<platform> and <arch> together affects INCLUDE, LIB, PATH, CPU, APPVER 
and TARGETOS environment variables. The last three are really 
interesting. They are consumed by win32.mak which sets preprocessor 
defines and command line options in accordance to passed CPU, APPVER and 
TARGETOS.

It seems we need to implement functionality of win32.mak as part of 
msvc.jam.

>>'<toolset-arch>' selects the target platform architecture. Sure this one 
>>works with PSDK only.
> Only for now. We should remember that later this feature will work for 
> other toolsets too.

Sure.

> msvc-config is deprecated, isn't it? I think the autodetection should be 
> built into main MSVC toolset. Or we should have -config pseudo-toolsets 
> for other compilers too.

I don't see any attempt to get rid of msvc-config.jam right now. While 
it is still exists I gathered all detection logic there. Later it will 
take 5 minutes to move all code from msvc-config.jam to msvc.jam.

> I can test:
> - MSVC 7.1. with and without PSDK
> - MSVC 8.0 (Team System June CTP) without PSDK (beta itself is newer 
> than any available external PSDK so there's no practical use for VS8.0 
> Standard edition and higher with external PSDK yet)
> 
> We'll also will need a support for VC 8.0 built-in 64-bit compilers. I'm 
> ready to contribute when all current pending patches will be integrated 
> or at least reviewed.

Great!

Best regards,
Alexey Pakhunov.