Merge pull request #3209 from TylerMSFT/twhitney-build

first draft

Author: garycentric

docs/build/projects-and-build-systems-cpp.md

@@ -1,14 +1,14 @@
 ---
 title: "C/C++ projects and build systems in Visual Studio"
-ms.description: "Use Visual Studio to compile and build C++ projects for Windows, ARM or Linux based on any project system."
+description: "Use Visual Studio to compile and build C++ projects for Windows, ARM, or Linux based on any project system."
 ms.date: "07/17/2019"
 helpviewer_keywords: ["builds [C++]", "C++ projects, building", "projects [C++], building", "builds [C++], options", "C++, build options"]
 ms.assetid: fa6ed4ff-334a-4d99-b5e2-a1f83d2b3008
 ms.topic: "overview"
 ---
 # C/C++ projects and build systems in Visual Studio
 
-You can use Visual Studio to edit, compile and build any C++ code base with full IntelliSense support without having to convert that code into a Visual Studio project or compile with the MSVC toolset. For example, you can edit a cross-platform CMake project in Visual Studio on a Windows machine, then compile it for Linux using g++ on a remote Linux machine.
+You can use Visual Studio to edit, compile, and build any C++ code base with full IntelliSense support without having to convert that code into a Visual Studio project or compile with the MSVC toolset. For example, you can edit a cross-platform CMake project in Visual Studio on a Windows machine, then compile it for Linux using g++ on a remote Linux machine.
 
 ## C++ compilation
 
@@ -22,25 +22,25 @@ Basic C++ compilation involves three main steps:
 
 ## The MSVC toolset
 
-The Microsoft C++ compiler, linker, standard libraries, and related utilities comprise the MSVC compiler toolset (also called a toolchain or "build tools"). These are included in Visual Studio. You can also download and use the toolset as a standalone package for free from the [Build Tools for Visual Studio 2019 download location](https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2019).
+The Microsoft C++ compiler, linker, standard libraries, and related utilities make up the MSVC compiler toolset (also called a toolchain or "build tools"). These are included in Visual Studio. You can also download and use the toolset as a free standalone package from [Build Tools for Visual Studio 2019 download](https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2019).
 
 You can build simple programs by invoking the MSVC compiler (cl.exe) directly from the command line. The following command accepts a single source code file, and invokes cl.exe to build an executable called *hello.exe*:
 
 ```cmd
 cl /EHsc hello.cpp
 ```
 
-Note that here the compiler (cl.exe) automatically invokes the C++ preprocessor and the linker to produce the final output file.  For more information, see [Building on the command line](building-on-the-command-line.md).
+Here the compiler (cl.exe) automatically invokes the C++ preprocessor and the linker to produce the final output file. For more information, see [Building on the command line](building-on-the-command-line.md).
 
 ## Build systems and projects
 
-Most real-world programs use some kind of *build system* to manage complexities of compiling multiple source files for multiple configurations (i.e. debug vs. release), multiple platforms (x86, x64, ARM, and so on), custom build steps, and even multiple executables that must be compiled in a certain order. You make settings in a build configuration file(s), and the build system accepts that file as input before it invoke the compiler. The set of source code files and build configuration files needed to build an executable file is called a *project*.
+Most real-world programs use some kind of *build system* to manage complexities of compiling multiple source files for multiple configurations (debug vs. release), multiple platforms (x86, x64, ARM, and so on), custom build steps, and even multiple executables that must be compiled in a certain order. You make settings in a build configuration file(s), and the build system accepts that file as input before it invoke the compiler. The set of source code files and build configuration files needed to build an executable file is called a *project*.
 
 The following list shows various options for Visual Studio Projects - C++:
 
 - create a Visual Studio project by using the Visual Studio IDE and configure it by using property pages. Visual Studio projects produce programs that run on Windows. For an overview, see [Compiling and Building](/visualstudio/ide/compiling-and-building-in-visual-studio) in the Visual Studio documentation.
 
-- open a folder that contains a CMakeLists.txt file. CMake support is integrated into Visual Studio. You can use the IDE to edit, test and debug without modifying the CMake files in any way. This enables you to work in the same CMake project as others who might be using different editors. CMake is the recommended approach for cross-platform development. For more information, see [CMake projects](cmake-projects-in-visual-studio.md).
+- open a folder that contains a CMakeLists.txt file. CMake support is integrated into Visual Studio. You can use the IDE to edit, test, and debug without modifying the CMake files in any way. This enables you to work in the same CMake project as others who might be using different editors. CMake is the recommended approach for cross-platform development. For more information, see [CMake projects](cmake-projects-in-visual-studio.md).
 
 - open a loose folder of source files with no project file. Visual Studio will use heuristics to build the files. This is an easy way to compile and run small console applications. For more information, see [Open Folder projects](open-folder-projects-cpp.md).
 
@@ -50,45 +50,45 @@ The following list shows various options for Visual Studio Projects - C++:
 
 ## MSBuild from the command line
 
-You can invoke MSBuild from the command line by passing it a .vcxproj file along with command-line options. This approach requires a good understanding of MSBuild, and is recommended only when absolutely necessary. For more information, see [MSBuild](msbuild-visual-cpp.md).
+You can invoke MSBuild from the command line by passing it a .vcxproj file along with command-line options. This approach requires a good understanding of MSBuild, and is recommended only when necessary. For more information, see [MSBuild](msbuild-visual-cpp.md).
 
 ## In This Section
 
-[Visual Studio projects](creating-and-managing-visual-cpp-projects.md)
+[Visual Studio projects](creating-and-managing-visual-cpp-projects.md)\
 How to create, configure, and build C++ projects in Visual Studio using its native build system (MSBuild).
 
-[CMake projects](cmake-projects-in-visual-studio.md)
+[CMake projects](cmake-projects-in-visual-studio.md)\
 How to code, build, and deploy CMake projects in Visual Studio.
 
-[Open Folder projects](open-folder-projects-cpp.md)
-How to use Visual Studio to code, build and deploy C++ projects based on any arbitrary build system, or no build system. at all.
+[Open Folder projects](open-folder-projects-cpp.md)\
+How to use Visual Studio to code, build, and deploy C++ projects based on any arbitrary build system, or no build system at all.
 
-[Release builds](release-builds.md)
+[Release builds](release-builds.md)\
 How to create and troubleshoot optimized release builds for deployment to end users.
 
-[Use the MSVC toolset from the command line](building-on-the-command-line.md)<br/>
+[Use the MSVC toolset from the command line](building-on-the-command-line.md)\
 Discusses how to use the C/C++ compiler and build tools directly from the command line rather than using the Visual Studio IDE.
 
-[Building DLLs in Visual Studio](dlls-in-visual-cpp.md)
-How to create, debug and deploy C/C++ DLLs (shared libraries) in Visual Studio.
+[Building DLLs in Visual Studio](dlls-in-visual-cpp.md)\
+How to create, debug, and deploy C/C++ DLLs (shared libraries) in Visual Studio.
 
-[Walkthrough: Creating and Using a Static Library](walkthrough-creating-and-using-a-static-library-cpp.md)
-How to create a .lib binary file.
+[Walkthrough: Creating and Using a Static Library](walkthrough-creating-and-using-a-static-library-cpp.md)\
+How to create a **.lib** binary file.
 
-[Building C/C++ Isolated Applications and Side-by-side Assemblies](building-c-cpp-isolated-applications-and-side-by-side-assemblies.md)
+[Building C/C++ Isolated Applications and Side-by-side Assemblies](building-c-cpp-isolated-applications-and-side-by-side-assemblies.md)\
 Describes the deployment model for Windows Desktop applications, based on the idea of isolated applications and side-by-side assemblies.
 
-[Configure C++ projects for 64-bit, x64 targets](configuring-programs-for-64-bit-visual-cpp.md)
+[Configure C++ projects for 64-bit, x64 targets](configuring-programs-for-64-bit-visual-cpp.md)\
 How to target 64-bit x64 hardware with the MSVC build tools.
 
-[Configure C++ projects for ARM processors](configuring-programs-for-arm-processors-visual-cpp.md)
+[Configure C++ projects for ARM processors](configuring-programs-for-arm-processors-visual-cpp.md)\
 How to use the MSVC build tools to target ARM hardware.
 
-[Optimizing Your Code](optimizing-your-code.md)
+[Optimizing Your Code](optimizing-your-code.md)\
 How to optimize your code in various ways including program guided optimizations.
 
-[Configuring Programs for Windows XP](configuring-programs-for-windows-xp.md)
+[Configuring Programs for Windows XP](configuring-programs-for-windows-xp.md)\
 How to target Windows XP with the MSVC build tools.
 
-[C/C++ Building Reference](reference/c-cpp-building-reference.md)<br/>
+[C/C++ Building Reference](reference/c-cpp-building-reference.md)\
 Provides links to reference articles about program building in C++, compiler and linker options, and various build tools.

docs/linux/configure-a-linux-project.md

@@ -1,6 +1,6 @@
 ---
 title: "Configure a Linux MSBuild C++ project in Visual Studio"
-ms.date: "08/06/2020"
+ms.date: "10/16/2020"
 description: "Configure a MSBuild-based Linux project in Visual Studio so you can build it."
 ms.assetid: 4d7c6adf-54b9-4b23-bd23-5de0c825b768
 ---
@@ -20,7 +20,7 @@ You can configure a Linux project to target a physical Linux machine, a virtual
 
 **Visual Studio 2019 version 16.1**:
 
-- When targeting WSL, you can avoid the copy operations that are necessary for building and IntelliSense when targeting remote Linux systems.
+- When you target WSL, you can avoid the copy operations needed to build and get IntelliSense that are required when you target a remote Linux system.
 
 - You can specify separate Linux targets for building and debugging.
 
@@ -34,6 +34,10 @@ To view configuration options, select the **Project > Properties** menu, or righ
 
 By default, an executable (.out) is built. To build a static or dynamic library, or to use an existing Makefile, use the **Configuration Type** setting.
 
+If you're building for Windows Subsystem for Linux (WSL), WSL Version 1 is limited to 64 parallel compilation processes. This is governed by the **Max Parallel Compilation Jobs** setting in **Configuration properties > C/C++ > General**.
+
+Regardless of the WSL version you are using, if you intend to use more than 64 parallel compilation processes, we recommend that you build with Ninja--which generally will be faster and more reliable. To build with Ninja, use the **Enable Incremental Build** setting in **Configuration properties > General**.
+
 For more information about the settings in the property pages, see [Linux Project Property Page Reference](prop-pages-linux.md).
 
 ## Remote settings
@@ -46,7 +50,7 @@ To change settings related to the remote Linux computer, configure the remote se
 
    ::: moniker range="vs-2019"
 
-   **Visual Studio 2019 version 16.1**: To target Windows Subsystem for Linux, click the down arrow for **Platform Toolset** and choose **WSL_1_0**. The other remote options will disappear and the path to the default WSL shell will appear in their place:
+   **Visual Studio 2019 version 16.7**: To target Windows Subsystem for Linux (WSL), set the **Platform Toolset** drop-down to **GCC for Windows Subsystem for Linux**. The other remote options will disappear and the path to the default WSL shell will appear in their place:
 
    ![WSL build machine](media/wsl-remote-vs2019.png)
 
@@ -61,7 +65,7 @@ To change settings related to the remote Linux computer, configure the remote se
 - The **Remote Build Project Directory** is where this specific project will be built on the remote Linux computer. This will default to **$(RemoteRootDir)/$(ProjectName)**, which will expand to a directory named after the current project, under the root directory set above.
 
 > [!NOTE]
-> To change the default C and C++ compilers, or the Linker and Archiver used to build the project, use the appropriate entries in the **C/C++ > General** section and the **Linker > General** section. You can specify a certain version of GCC or Clang, for example. For more information see [C/C++ Properties (Linux C++)](prop-pages/c-cpp-linux.md) and [Linker Properties (Linux C++)](prop-pages/linker-linux.md).
+> To change the default C and C++ compilers, or the Linker and Archiver used to build the project, use the appropriate entries in the **C/C++ > General** section and the **Linker > General** section. You can specify a certain version of GCC or Clang, for example. For more information, see [C/C++ Properties (Linux C++)](prop-pages/c-cpp-linux.md) and [Linker Properties (Linux C++)](prop-pages/linker-linux.md).
 
 ## Copy sources (remote systems only)
 
@@ -100,7 +104,7 @@ This functionality depends on the Linux machine having zip installed. You can in
 sudo apt install zip
 ```
 
-To manage your header cache, navigate to **Tools > Options, Cross Platform > Connection Manager > Remote Headers IntelliSense Manager**. To update the header cache after making changes on your Linux machine, select the remote connection and then select **Update**. Select **Delete** to remove the headers without deleting the connection itself. Select **Explore** to open the local directory in **File Explorer**. Treat this folder as read-only. To download headers for an existing connection that was created prior to Visual Studio 2017 version 15.3, select the connection and then select **Download**.
+To manage your header cache, navigate to **Tools > Options, Cross Platform > Connection Manager > Remote Headers IntelliSense Manager**. To update the header cache after making changes on your Linux machine, select the remote connection and then select **Update**. Select **Delete** to remove the headers without deleting the connection itself. Select **Explore** to open the local directory in **File Explorer**. Treat this folder as read-only. To download headers for an existing connection that was created before Visual Studio 2017 version 15.3, select the connection and then select **Download**.
 
 ::: moniker range="vs-2017"