From: Alexey Pakhunov (alexeypa_at_[hidden])
Date: 2005-08-02 02:25:04
Andrey Melnikov wrote:
>Now after review by Vladimir I sent a new version of my patch. So you
>need to merge my changes again.
Done. I'm working on supporting amd64 and ia64 by VS 8. I will post an
updated patch soon.
>><platform> and <arch> together affect 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
>>It seems we need to implement functionality of win32.mak as part of
>Is our ultimate goal to make external and built-in psdk builds using the
>same set of compiler settings?
win32.mak deals with a quite reasonable subset of settings:
- defines: WINVER, _WINNT, _WIN95, _WIN32_WINNT, _WIN32_WINDOWS,
_WIN32_IE, _X86_, _IA64_, _AMD64_, WIN64, _WIN64, WIN32, _WIN32
- compiler flags: -W3, -W4, -Wp64, -GS
- midl flags
- default libraries
It is logical to use at least some of them since we've got <platform>
and <arch> settings.
>Besides patch autodetection msvc-config also runs "using msvc" rule
>several times for each of the autodetected versions.
>Can this functionality be built into msvc.jam? Should it?
Sure, it is possible. We can freely move this code around depending on
what the decision will be taken about x-config files.
> b) We still haven't decided on a common toolset configuration description.
So once it will be defined I will be able to move the code accordingly.
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