|
1 | 1 | --- |
2 | 2 | title: "CMake Projects in Visual C++ | Microsoft Docs" |
3 | 3 | ms.custom: "" |
4 | | -ms.date: "09/26/2018" |
| 4 | +ms.date: "10/18/2018" |
5 | 5 | ms.reviewer: "" |
6 | 6 | ms.suite: "" |
7 | 7 | ms.technology: ["cpp-ide"] |
@@ -79,7 +79,7 @@ Not everything in the cache is imported. Properties such as the generator and t |
79 | 79 | To build a CMake project, you have these choices: |
80 | 80 |
|
81 | 81 | 1. Select the target in the **Debug** dropdown and press **F5**, or click the **Run** (green triangle) button. The project automatically builds first, just like a Visual Studio solution. |
82 | | -1. Right click on the CMakeLists.txt and select **Build** from the context menu. If you have multiple targets in your folder structure, you can choose to build all or only one specific target, or |
| 82 | +1. Right click on the CMakeLists.txt and select **Build** from the context menu. If you have multiple targets in your folder structure, you can choose to build all or only one specific target. |
83 | 83 | 1. From the main menu, select **Build | Build Solution** (**F7** or **Ctrl+Shift+B**). Make sure that a CMake target is already selected in the **Startup Item** dropdown in the **General** toolbar. |
84 | 84 |
|
85 | 85 |  |
@@ -205,7 +205,7 @@ To specify a Visual Studio generator, open the CMakeSettings.json from the main |
205 | 205 |
|
206 | 206 | 1. **buildRoot**: maps to **-DCMAKE_BINARY_DIR** switch and specifies where the CMake cache will be created. If the folder does not exist, it is created. |
207 | 207 |
|
208 | | -1. **variables**: contains a name-value pair of CMake variables that will get passed as **-D**_name_**=**_value_ to CMake. If your CMake project build instructions specify the addition of any variables directly to the CMake cache file, it is recommended that you add them here instead. The following example shows how to specify the name-value pairs: |
| 208 | +1. **variables**: contains a name-value pair of CMake variables that will get passed as **-D** *_name_=_value_* to CMake. If your CMake project build instructions specify the addition of any variables directly to the CMake cache file, it is recommended that you add them here instead. The following example shows how to specify the name-value pairs: |
209 | 209 |
|
210 | 210 | ```json |
211 | 211 | "variables": [ |
@@ -275,7 +275,7 @@ CMakeSettings.json now supports inherited environments. This feature enables you |
275 | 275 |
|
276 | 276 | The example above is the same as running the **Developer Command Prompt for VS 2017** with the **-arch=amd64 -host_arch=amd64** arguments. |
277 | 277 |
|
278 | | -The following table shows the default values and their command line equivalents: |
| 278 | +The following table shows the default values: |
279 | 279 |
|
280 | 280 | |Context Name|Description| |
281 | 281 | |-----------|-----------------| |
|
0 commit comments