Visual C + + contains compilers that you can use to create apps that run on 32-bit, 64-bit, or ARM-based Windows operating systems.
The following list describes the various versions of the cl.exe (Visual C + + compiler):
-
-
x86 on x86
-
-
Use this to create an output file for the x86 computer. This version of cl.exe runs as a 32-bit native process on the x86 computer and under WOW64 in a 64-bit Windows operating system.
-
-
x64 on x86 (x64 cross-platform compiler)
-
-
Use this to create a x64 output file. This version of cl.exe runs as a 32-bit native process on the x86 computer and under WOW64 in a 64-bit Windows operating system.
-
-
x64 on x64
-
-
Use this to create a x64 output file. This version of cl.exe runs as a native process on the x64 computer.
-
-
Arm on x86 (arm cross-platform compiler)
-
-
Use this to create an output file for an ARM device. This version of cl.exe runs as a 32-bit native process on the x86 computer and under WOW64 in a 64-bit Windows operating system.
When you install a 64-bit Windows operating system in Visual Studio, the various 64-bit native compiler command prompts and cross-platform compilers are available.Access these command prompts in Windows 8, start screen, open all apps. microsoft Visual Studio, choose one of the Native-tool or Cross-tool command prompts. " > under microsoft Visual Studio, select a native tool or a cross-tool command prompt. start, expand all Programs, microsoft Visual Studio, and visual Studio Tools, and then choose a Command prompt. " In earlier versions of Windows, select All Programs, visual Studio tool, then select Command Prompt.
Vcvarsall.bat Any compiler that enables the compiler toolset can be used at the command line to configure paths and environment variables by running the Vcvarsall.bat batch file. By default, the full path to this file is or C:\Program Files\Microsoft Visual Studio X.x\vc\vcvarsall.bat on a 32-bit Windows operating system or C:\Program files (x86) \microsoft Visual Studio X.X\VC \ Vcvarsall.bat on 64-bit systems.
If no parameters are provided, the Vcvarsall.bat batch file configures the environment variable to use the x86,32-bit compiler. However, you can use this configuration for any compiler. If you specify a compiler configuration that is not yet installed in your build computer architecture, an error message will be displayed. The following table shows the supported parameters.
vcvarsall.bat parameter |
compiler |
Generate computer architecture |
Build Out architecture |
x86 |
32-bit native compiler |
X86,x64 |
x86 |
X86_amd64 |
x64 Cross-platform compilers |
X86,x64 |
x64 |
Amd64 |
x64 native Compiler |
x64 |
x64 |
X86_arm |
ARM Cross |
X86,x64 |
Arm |
/machine:{arm| ebc| ia64| mips| mips16| mipsfpu| mipsfpu16| sh4| thumb| x64| X86}NotesThe/MACHINE option specifies the target platform for the program.
linker tools Error LNK1113. " However, in some cases, link cannot determine the machine type and issue linker tool error LNK1113.
The link module machine type "x64" conflicts with the target machine type "X86" Conflict emit linker tool error LNK1113 because the CL program that generated the object file is x64 but the/machine:x86 specified by link
To enable the 64-bit Visual C + + toolset on the command line