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
When both path and version are merged in the .props file discussion, a division between the .props approach and the IDE approach seems more natural than repeating the same content twice.
Copy file name to clipboardExpand all lines: docs/build/clang-support-msbuild.md
+8-21Lines changed: 8 additions & 21 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
description: "Learn more about: Clang/LLVM support in Visual Studio projects"
3
3
title: "Clang/LLVM support in Visual Studio projects"
4
-
ms.date: 06/29/2022
4
+
ms.date: 09/20/2022
5
5
ms.description: "Configure a Visual Studio MSBuild project to use the Clang/LLVM toolchain."
6
6
helpviewer_keywords: ["Clang support for C++ MSBuild projects"]
7
7
---
@@ -52,9 +52,9 @@ To configure a Visual Studio Linux project to use Clang:
52
52
53
53
On Linux, Visual Studio by default uses the first Clang location that it finds in the PATH environment property. If you're using a custom Clang installation, then either change the value of the `LLVMInstallDir` property or else enter the path under **Project** > **Properties** > **Configuration Properties** > **VC++ DIrectories** > **Executable Directories**. For more information, see [Set a custom LLVM location](#custom_llvm_location).
54
54
55
-
## <aname="custom_llvm_location"></a> Set a custom LLVM location
55
+
## <aname="custom_llvm_location"></a> Set a custom LLVM location and toolset
56
56
57
-
You can set a custom path to LLVM for one or more projects by creating a *Directory.build.props* file. Then, add that file to the root folder of any project. You can add it to the root solution folder to apply it to all projects in the solution. The file should look like this (but use your actual LLVM path and version number):
57
+
To set a custom path to LLVM and set a custom LLVM toolset version for one or more projects, create a *Directory.build.props* file. Then, add that file to the root folder of any project. You can add it to the root solution folder to apply it to all projects in the solution. The file should look like this example (but use your actual LLVM path and version number):
58
58
59
59
```xml
60
60
<Project>
@@ -65,36 +65,23 @@ You can set a custom path to LLVM for one or more projects by creating a *Direct
65
65
</Project>
66
66
```
67
67
68
-
You can combine this property with a custom LLVM toolset version. For more information, see [Set a custom LLVM toolset version](#custom_llvm_toolset).
68
+
## <aname="custom_llvm_toolset"></a> Set a custom LLVM toolset version in the IDE
69
69
70
-
## <aname="custom_llvm_toolset"></a> Set a custom LLVM toolset version
70
+
Starting in Visual Studio 2019 version 16.9, you can set a custom toolset version for LLVM in Visual Studio. To set this property in a project:
71
71
72
-
Starting in Visual Studio 2019 version 16.9, you can set a custom toolset version for LLVM. To set this property in a project in Visual Studio:
73
-
74
-
1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](./working-with-project-properties.md).
72
+
1. Open the project's **Property Pages** dialog box. For more information, see [Set C++ compiler and build properties](./working-with-project-properties.md).
75
73
76
74
1. Select the **Configuration Properties** > **General** property page.
77
75
78
-
1. Modify the **Platform Toolset** property to *LLVM (clang-cl)*, if it isn't already set.
76
+
1. Modify the **Platform Toolset** property to *LLVM (clang-cl)*, if it isn't already set. Choose **Apply** to save your changes.
79
77
80
78
1. Select the **Configuration Properties** > **Advanced** property page.
81
79
82
80
1. Modify the **LLVM Toolset Version** property to your preferred version, and then choose **OK** to save your changes.
83
81
84
82
The **LLVM Toolset Version** property only appears when the LLVM platform toolset is selected.
85
83
86
-
You can set the toolset version for one or more projects by creating a *Directory.build.props* file. Then, add that file to the root folder of any project. Add it to the root solution folder to apply it to all projects in the solution. The file should look like this (but use your actual LLVM path and version number):
87
-
88
-
```xml
89
-
<Project>
90
-
<PropertyGroup>
91
-
<LLVMInstallDir>C:\MyLLVMRootDir</LLVMInstallDir>
92
-
<LLVMToolsVersion>15.0.0</LLVMToolsVersion>
93
-
</PropertyGroup>
94
-
</Project>
95
-
```
96
-
97
-
When you add a *Directory.build.props* file, the settings appear as the default in the project Property Pages dialog. However, changes to these properties in Visual Studio override the settings in the *Directory.build.props* file.
84
+
When you add a *Directory.build.props* file to a project or solution, the settings appear as the default in the project Property Pages dialog. However, changes to these properties in Visual Studio override the settings in the *Directory.build.props* file.
98
85
99
86
## Set additional properties, edit, build, and debug
0 commit comments