How to compile x64 code with Visual Studio in comm

Question

I want to compile a simple hello-world-style program using the Windows command line.

cl file_name.c

is easy enough. Now I want to do the same thing in 64 Bit. What should I do?

Answer 1

As others have mentioned the answer depends on whether you are using a native x64 compiler or the cross compiler. This webpage should help you http://msdn.microsoft.com/en-us/library/x4d2c09s.aspx

Answer 2

You need to use a version of the cl.exe compiler which emits x64 code. Which one depends a bit on your setup.

Let's consider the case you're on a 64 bit machine. For this you'll need to use the compiler which lives at

c:\Program Files (x86)\Microsoft visual Studio 10.0\VC\bin\amd64\cl.exe

If you're on a 32 bit machine you'll need to use the cross compiler located at

c:\Program Files\Microsoft Visual Studio 10.0\VC\bin\x86_amd64\cl.exe

Answer 3

If you have code as a part of project you can use as below

"C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe" myproject.sln /Build "Release|x64"

got from below link

http://social.msdn.microsoft.com/Forums/en-US/vcgeneral/thread/ed855b9d-55ef-49f1-bf27-f20a79be687e

Answer 4

Run cl from a Visual Studio x64 Command Prompt.

Answer 5

Kyle is right. It is just a matter of setting the PATH environment variable properly. The regular x86 compiler lives in the vc\bin subdirectory. There are two 64-bit compilers, a 32-bit compiler that generates 64-bit code in vc\bin\x86_amd64 and a 64-bit compiler that generates 64-bit code in vc\bin\amd64.

The default Visual Studio setup always uses the 32-bit compiler to generate 64-bit code.

Note that the 64-bit compilers are not installed by default. You'll have to re-run setup.exe if you didn't use the custom install option. And re-run the SP1 installer.

Answer 6

Run cl from a "Visual Studio x64 Command Prompt" or something similar like "x64 Native Tools Command Prompt for VS 2017". Run where cl to see the path of which "cl" you're running. Something like "x64" or "amd64" should be in the path.

The start menu search can be unhelpful at times. Try typing "vs20xx" or "vs 20xx" instead of "visual studio" to find it. The name of the prompt changes over releases. If it does not say "64", then it will set up a 32 bit environment.

The 64 prompt tends to just call "Vcvarsall.bat" with a 64 argument, but the argument changes over time and may not be backwards compatible.