Re: [cdt-dev] Bug 385608 - Comment

[BONNEAU Guy <Guy.Bonneau@xxxxxxxxxxx>]

I didn't know that was already possible with another C++ toolchain to setup compiler option! That's great and that's the way it should be. Having a WIN32 / x86_64 (AMD64)  option capability to choose the compiler and thus the path would even allow cross platform compilation of x86_64 under Windows 32 bits OS with Eclipse CDT since the x86_64 Visual Studio C++ compiler is natively a 32 bits application and can be installed in a Windows 32 bits environment!

I agree! 

Guy

________________________________________
From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Marc-Andre Laperle [malaperle@xxxxxxxxx]
Sent: Wednesday, September 19, 2012 11:10 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Bug 385608 - Comment

Hi Guy,

As a user, I would prefer something more obvious like choosing the
target platform in the new project wizard. Of course, it should also be
possible to change the target platform in an existing project but I'm
not sure setting an environment variable is the most obvious way to
control that. Perhaps it should work like the "compiler version" seen in
the XLC toolchain, see attachment. For XLC, the compiler version can be
set in a page in project wizard as well as a property page in the
project properties. What do you think?

Marc-Andre

On 9/19/2012 10:56 AM, BONNEAU Guy wrote:
> I'm not sure if a CDT architecture has been planned to help build both 32/64 bits applications using the Microsoft Visual toolchain with the same instance of Eclipse. But I believe it might be possible to workaround the issue with a simple predefined variables added to the native environment of the C/C++ Build of the project: by using the C/C++ Build/Environment project panel of Eclipse.
>
> This predefined variable could be set by default to a false status to build a 32 bits application by default. Override of this variable to a true status would request a 64 bits application. Then the WinEnvironmentVariableSupplier Class could easily setup the appropriate Visual Studio path to either the 32 bits or 64 bits Microsoft include/library/bin by accessing this environment variable which would enable either 32 or 64 application build.
>
> This would similar to what Visual Studio is doing with the configuration manager to choose either a Win32 or x64 solution and determine the appropriate tools to be used. I believe this would be an easy fix to do.
>
> Regards
> Guy Bonneau
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev