[Scons-dev] SCons building with MS Visual C++10 on 64-bit Windows.

[Edward d'Auvergne]

That's true, I didn't think about this warning becoming annoying.
This code path look like it is hit up to 10 times with the scons
initialisation, so you'd end up with 10 identical warning messages
anyway.  So a warning is clearly not the best idea.  As for the 64-bit
compiler, if its there along with the 32-bit compiler, the 64-bit
compiler should be used by default.  I would assume that to be
reasonable.  But if only one is present (either 64-bit or 32-bit),
then it's clearly better to default to the one present rather than to
not initialise the compiler environment and hence end up with neither.
 If you have both installed and you want to compile differently, then
setting the TARGET_ARCH should be expected.  Is there some scenario
where such logic fails?

Regards,

Edward


On 15 June 2012 17:39, Gary Oberbrunner <garyo at oberbrunner.com> wrote:

> On Fri, Jun 15, 2012 at 11:12 AM, Edward d'Auvergne

> <edward at nmr-relax.com> wrote:

>>  If you like though, I

>> can add a warning to my proposed changes through the

>> SCons.Warnings.warn() system stating that scons is falling back to the

>> 32-bit compiler.

>

> Grumble... this is of course a good idea, EXCEPT that on Windows the

> Visual Studio tools are run by default whether you're actually using

> them or not.  So people using SCons for LaTeX (for example) would see

> this warning, even though they don't care at all about C/C++ programs.

>  We have a project to revamp how Tools are created and used which

> would address this, but it's a big job.

> (http://www.scons.org/wiki/PlatformToolConfigAlt and

> http://www.scons.org/wiki/PlatformToolConfig)

>

> It might be OK just to give your warning in the case where you're on a

> 64 bit system, so TARGET_ARCH has defaulted to 64 bit, but you have

> only 32 bit MSVC (but say nothing if you have no MSVC at all).  But

> perhaps it would be better to not default TARGET_ARCH so early, so we

> could tell what the user's intent is -- if they don't specify

> TARGET_ARCH, try all.  That's kind of what you're looking for, right?

> (though in your particular case, you'd probably rather it never

> produce a 64-bit build).

>

> --

> Gary

> _______________________________________________

> Scons-dev mailing list

> Scons-dev at scons.org

> http://two.pairlist.net/mailman/listinfo/scons-dev