64-bit Win7 with VC10Expr requires TARGET_ARCH="x86"

[bdbaddog]

This issue was originally created at: 2010-07-27 00:29:43.
This issue was reported by: carstenf.
carstenf said at 2010-07-27 00:29:43

Using a 64-bit Windows 7 with VC10 Express requires TARGET_ARCH="x86" in the Environment constructor, because the Express Editions don't have a 64-bit compiler included.

As there is no way to succesfully achieve x86_64 builds in this situation, SCons should automatically fall back to x86 target_arch, instead of failing silently.

Other compiler versions (VC9Expr, VC8Expr) have not been tested - they may be affected as well.

gregnoel said at 2010-08-08 12:55:02

Bug party triage.

bdbaddog said at 2010-08-22 17:23:43

Fixed checked in.
Please try from trunk.

Checked in potential fix in revision 5163

Sending src/CHANGES.txt
Sending src/RELEASE.txt
Sending src/engine/SCons/Tool/MSCommon/vs.py
Transmitting file data ...
Committed revision 5163.

garyo said at 2012-09-01 10:01:49

Bumping all old issues targeted for past releases to 2.x.

ajf58 said at 2014-07-10 05:03:51

If the fix was committed 4 years ago can we confirm this as fixed?

[mwichmann]

@jcbrill since this never ends...

[jcbrill]

This is effectively the same as the open #2697 and the closed #2844.

This issue is associated with version 2.0.0.final.0.

As documented in #2884, the TARGET_ARCH is required when using python 2.7/3.2+ for versions of scons less than 2.4.0 due to the default setting of TARGET_ARCH=HOST_ARCH.

In the current version, when only VS2010 Express is installed, the TARGET_ARCH is not necessary but the build will fail if MSVC_VERSION is not specified. This behavior is identical to #2697: the detection fails. Without an MSVC_VERSION there is no detected default version and the build silently fails. Passing a MSVC_VERSION=10.0Exp works with an SCons warning that no versions were detected.

At this point, this issue is effectively a duplicate of #2697. There doesn't seem to be much point in keeping both open. As there is more discussion (spammed by the author) in #2697, it is not the end of the world to close this issue as the behavior at the time was rectified in scons 2.4.0 (like #2844).

[mwichmann]

Fine, let's close it then.