What is the difference between x64 Native Tools Command Prompt and x64 Cross Tools Command Prompt?

windows visual-studio visual-c++ command-prompt
Abhishek Jain picture Abhishek Jain · Dec 2, 2014 · Viewed 9.5k times · Source

I have installed 32 bit Visual Studio 2013 on my 64 bit Windows 8.1. I have 5 command prompts:

  1. Developer Command Prompt for VS2013
  2. VS2013 ARM Cross Tools Command Prompt
  3. VS2013 x64 Cross Tools Command Prompt
  4. VS2013 x64 Native Tools Command Prompt
  5. VS2013 x86 Native Tools Command Prompt

I do not understand the difference between:

  1. Developer Command Prompt for VS2013 Versus VS2013 x86 Native Tools Command Prompt
  2. VS2013 x64 Cross Tools Command Prompt Versus VS2013 x64 Native Tools Command Prompt

Answer

Hans Passant picture Hans Passant · Dec 2, 2014

A cross compiler is a compiler that executes on one platform but generates code for another. Your machine has two compilers that can generate x64 code. One is the 32-bit cross compiler in the vc/bin/amd64_x86 directory, the other is a 64-bit native compiler in the vc/bin/amd64 directory. They both generate the exact same x64 machine code.

You only must use the cross compiler when you have a 32-bit operating system. Debugging and testing the program it generates is unpleasant, you need another machine and use the remote debugger. Okay for a build server, perhaps. If you have the 64-bit version of Windows then either choice is fine, but you favor the "x64 Native" selection. The compiler and linker are slightly faster and can tackle much bigger programs.

This also explains why you only have the cross compiler selection for ARM, you don't have an ARM processor in your dev machine.

Related questions

What version of Visual Studio is Python on my computer compiled with?

I am trying to find out the version of Visual Studio that is used to compile the Python on my computer It says Python 2.6.2 (r262:71605, Apr 14 2009, 22:40:02) [MSC v.1500 32 bit (Intel)] on win32 What I do not understand is this MSC …

Read More
Visual Studio compiles but the exe isn't there

Source code that compiles fine on other peoples environments won't correctly work in my environment. When I do a rebuild the compile occurs but when visual studio goes to move the exe from /obj/debug/{solution} to /debug/{solution} it …

Read More
Should I define both _WIN32 and _WIN64 in 64bit build?

When we add a 64bit configuration from a 32bit project that has already existed, Visual Studio copies the 32bit configurations by default. VS even copies _WIN32 All my 64bit projects define also _WIN32 now, despite they(64bit PEs) never can …

Read More