Use the Microsoft C++ toolset from the command line
MSBuild on the command line - C++
Create C++ cross-platform projects
Cross Platform C++ Development
Linux && arm cross compaling in visual studio code
- Build from the Command Line
1.1 Download and install the tools
1.2 How to use the command-line tools
1.3 Path and environment variables for command-line builds
1.4 Developer command prompt shortcuts - Create Cpp Cross-Platform Projects
- Cross Platform C++ Development
- Customize IDE for build and debug tasks
You can build C and C++ applications on the command line by using tools that are included in Visual Studio. The Microsoft C++ (MSVC) compiler toolset is also downloadable as a standalone package. You don't need to install the Visual Studio IDE if you don't plan to use it.
Note
This article is about how to set up an environment to use the individual compilers, linkers, librarian, and other basic tools. The native project build system, MSBuild, does not use the environment as described in this article. For more information on how to use MSBuild from the command line, see MSBuild on the command line - C++.
If you've installed Visual Studio and a C++ workload, you have all the command-line tools. For information on how to install C++ and Visual Studio, see Install C++ support in Visual Studio. If you only want the command-line toolset, download the Build Tools for Visual Studio. When you run the downloaded executable, it updates and runs the Visual Studio Installer. To install only the tools you need for C++ development, select the C++ build tools workload. You can select optional libraries and toolsets to include under Installation details. To build code by using the Visual Studio 2015 or 2017 toolsets, select the optional MSVC v140 or MSVC v141 build tools. When you're satisfied with your selections, choose Install.
When you choose one of the C++ workloads in the Visual Studio Installer, it installs the Visual Studio platform toolset. A platform toolset has all the C and C++ tools for a specific Visual Studio version. The tools include the C/C++ compilers, linkers, assemblers, and other build tools, and matching libraries. You can use all of these tools at the command line. They're also used internally by the Visual Studio IDE. There are separate x86-hosted and x64-hosted compilers and tools to build code for x86, x64, ARM, and ARM64 targets. Each set of tools for a particular host and target build architecture is stored in its own directory.
To work correctly, the tools require several specific environment variables to be set. These variables are used to add the tools to the path, and to set include file, library file, and SDK locations. To make it easy to set these environment variables, the installer creates customized command files, or batch files, during installation. You can run one of these command files to set a specific host and target build architecture, Windows SDK version, and platform toolset. For convenience, the installer also creates shortcuts in your Start menu. The shortcuts start developer command prompt windows by using these command files for specific combinations of host and target. These shortcuts ensure all the required environment variables are set and ready to use.
The required environment variables are specific to your installation and to the build architecture you choose. They also might be changed by product updates or upgrades. That's why we recommend you use an installed command prompt shortcut or command file, instead of setting the environment variables yourself.
The toolsets, command files, and shortcuts installed depend on your computer processor and the options you selected during installation. The x86-hosted tools and cross tools that build x86 and x64 code are always installed. If you have 64-bit Windows, the x64-hosted tools and cross tools that build x86 and x64 code are also installed. If you choose the optional C++ Universal Windows Platform tools, then the x86 and x64 tools that build ARM and ARM64 code also get installed. Other workloads may install these and other tools.
The MSVC command-line tools use the PATH, TMP, INCLUDE, LIB, and LIBPATH
environment variables, and also use other environment variables specific to your installed
tools, platforms, and SDKs. Even a simple Visual Studio installation may set twenty or more
environment variables. The values of these environment variables are specific to your
installation and your choice of build configuration, and can be changed by product updates
or upgrades. That's why we strongly recommend that you use a
developer command prompt shortcut
or one of the customized command files
to set them. We don't recommend you set them in the Windows environment yourself.
To see which environment variables are set by a developer command prompt shortcut, you can use
the SET command. Open a plain command prompt window and capture the output of the SET
command for a baseline. Open a developer command prompt window and capture the output of the
SET command for comparison. A diff tool such as the one built into the Visual Studio IDE can
be useful to compare the environment variables and see what's set by the developer command
prompt. For information about the specific environment variables used by the compiler and linker,
see CL Environment Variables.
The command prompt shortcuts are installed in a version-specific Visual Studio folder in your Windows Start menu. Here's a list of the base command prompt shortcuts and the build architectures they support:
- Developer Command Prompt - Sets the environment to use 32-bit, x86-native tools to build 32-bit, x86-native code.
- x86 Native Tools Command Prompt - Sets the environment to use 32-bit, x86-native tools to build 32-bit, x86-native code.
- x64 Native Tools Command Prompt - Sets the environment to use 64-bit, x64-native tools to build 64-bit, x64-native code.
- x86_x64 Cross Tools Command Prompt - Sets the environment to use 32-bit, x86-native tools to build 64-bit, x64-native code.
- x64_x86 Cross Tools Command Prompt - Sets the environment to use 64-bit, x64-native tools to build 32-bit, x86-native code.
The Start menu folder and shortcut names vary depending on the installed version of Visual Studio. If you set one, they also depend on the installation Nickname. For example, suppose you installed Visual Studio 2019, and you gave it a nickname of Latest. The developer command prompt shortcut is named Developer Command Prompt for VS 2019 (Latest), in a folder named Visual Studio 2019.
Note
Several command-line tools or tool options may require Administrator permission. If you have permission issues when you use them, we recommend that you open the developer command prompt window by using the Run as Administrator option. On Windows 10, right-click to open the shortcut menu for the command prompt window, then choose More, Run as administrator.
- Customize build and debug tasks for "Open Folder" development
- 如何在一个tasks.json中定义多个打字稿编译任务?
- VS Code 运行C++程序以及TASKS.JSON和LAUNCH.JSON文件的基础配置
- tasks.vs.json schema reference (C++)
- Visual Studio Macros for Build Commands & Property