FiveTech Support Forums

These past days we migrated FWH 64 from VS2010 to VS2012. So far so good.

Also it seems to be backwards compatible with VS2010, just compiling with the flag /GS-

But what we found, and we want to share this reminder with all of you, is that this is the right way to call the CL.EXE for 64 bits:

"$(VCINSTALLDIR)"bin\x86_amd64\cl.exe

Notice the x86_amd64 folder. If you don't use this one, you will end with OBJs not compatible with 64 bits.

Another good reminder:

We use CL.EXE C mode (/TC flag) to compile all FWH 64 files

This is also used from build64.bat

Antonio,

Since I am building with the 32bit version of Visual Studio 2012 ( I assume making 32 bit .exes ), then I assume those specifications do not need to be met. Although all new computers are generally 64 bit ( and run 32 bit software ), most of my clients have a mix of 32 and 64 bit OSs.

Tim

Antonio,

I am a bit confused.

With MSVC 2012 for 64 bits, can we also créate 32 bits?.

What compliers should we install?.

Tim,

The above only applies for building 64 bits apps using FWH 64 bits ahd Harbour 64 bits.

Elvira,

There is only one VS2012 (express, pro, ..., ultimate -crazy strategy from Microsoft that just confuses users-)

And that VS2012 provides the hability to build 32 and 64 bits apps. So you just have to install VS2012 and you are ready for 32 and 64 bits development

thats why I am enjoying Visual Studio 2012 more and more

Antonio,

Which versión of 2012?.

For Windows 8, For Desktop?.

And an exe build with MSVC 2012 32 bits, runs in XP mode?.

MSVC 2012 has two cl.exe and link.exe, one for 32 and other 64 or just one?.

Thnank you.

Lucas,

VS2012 Desktop

Yes, it properly runs on XP with this required minor fix:

viewtopic.php?p=149122#p149122

One for 32 and another for 64. Two different CL.EXE