You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a CMake project, build configurations are stored in a CMakeSettings.json file. When you choose **Manage Configurations** from the build configuration dropdown in the main toolbar, a dialog appears that shows the default CMake configurations available in Visual Studio:
11
-
- x86 Debug
10
+
::: moniker range="vs-2015"
11
+
12
+
CMake projects are supported in Visual Studio 2017 and later.
13
+
14
+
::: moniker-end
15
+
16
+
::: moniker range="vs-2017"
17
+
18
+
In a CMake project, build configurations are stored in a CMakeSettings.json file. When you choose **Manage Configurations** from the build configuration dropdown in the main toolbar, a dialog appears that shows the default CMake configurations available in Visual Studio:
19
+
- x86 Debug
12
20
- x86 Release
13
21
- x64 Debug
14
22
- x64 Release
@@ -17,9 +25,9 @@ In a CMake project, build configurations are stored in a CMakeSettings.json file
17
25
- IoT Debug
18
26
- IoT Release
19
27
- MinGW Debug
20
-
- MinGW Release
28
+
- MinGW Release
21
29
22
-
When you choose a configuration, it is added to the CMakeSettings.json file in the project's root folder. You can then use it to build your project.
30
+
When you choose a configuration, it is added to the CMakeSettings.json file in the project's root folder. You can then use it to build your project.
23
31
24
32
25
33
## Linux predefined build configurations:
@@ -337,7 +345,350 @@ These options allow you to run commands on the remote system before and after bu
337
345
]
338
346
}
339
347
```
348
+
::: moniker-end
349
+
350
+
::: moniker range="vs-2019"
351
+
352
+
In a CMake project, build configurations are stored in a CMakeSettings.json file. When you choose **Manage Configurations** from the build configuration dropdown in the main toolbar, a dialog appears that shows the default CMake configurations available in Visual Studio:
353
+
354
+
- x86 Debug
355
+
- x86 Clang Debug
356
+
- x86 Release
357
+
- x86 Clang Release
358
+
- x64 Debug
359
+
- x64 Clang Debug
360
+
- x64 Release
361
+
- x64 Clang Release
362
+
- Linux-Debug
363
+
- Linux-Release
364
+
- Linux-Clang-Debug
365
+
- Linux-Clang-Release
366
+
- Existing Cache (remote)
367
+
- Existing Cache
368
+
- MinGW Debug
369
+
- MinGW Release
370
+
- WSL Debug
371
+
- WSL Release
372
+
- WSL Clang Debug
373
+
- WSL Clang Release
374
+
- Clang
375
+
376
+
When you choose a configuration, it is added to the CMakeSettings.json file in the project's root folder. You can then use it to build your project.
Copy file name to clipboardExpand all lines: docs/build/cmakesettings-reference.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -114,7 +114,7 @@ When the active configuration specifies a Visual Studio generator, by default MS
114
114
115
115
-`remoteMachineName`: specifies the name of the remote Linux machine that hosts CMake, builds, and the debugger. Use the Connection Manager for adding new Linux machines. Supported macros include `${defaultRemoteMachineName}`.
116
116
-`remoteCopySourcesOutputVerbosity`: specifies the verbosity level of the source copying operation to the remote machine. May be one of ""Normal", "Verbose", or "Diagnostic".
117
-
-`remoteCopySourcesConcurrentCopies`: specifies the number of concurrent copies used during the synchronization of the sources to the remote machine.
117
+
-`remoteCopySourcesConcurrentCopies`: specifies the number of concurrent copies used during the synchronization of the sources to the remote machine (sftp only).
118
118
-`remoteCopySourcesMethod`: specifies the method to copy files to the remote machine. May be "rsync" or "sftp".
119
119
-`remoteCMakeListsRoot`: specifies the directory on the remote machine that contains the CMake project. Supported macros include `${workspaceRoot}`, `${workspaceHash}`, `${projectFile}`, `${projectDir}`, `${thisFile}`, `${thisFileDir}`, `${name}`, `${generator}`, `${env.VARIABLE}`.
120
120
-`remoteBuildRoot`: specifies the directory on the remote machine in which CMake generates build scripts for the chosen generator. Supported macros include `${workspaceRoot}`, `${workspaceHash}`, `${projectFile}`, `${projectDir}`, `${thisFile}`, `${thisFileDir}`, `${name}`, `${generator}`, `${env.VARIABLE}`.
0 commit comments