Skip to content

Commit c26ebab

Browse files
author
Colin Robertson
authored
Update per 2168 clang-cl.exe locations
Fixes a user-reported issue.
1 parent 10162c2 commit c26ebab

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

docs/build/clang-support-msbuild.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "Clang/LLVM support in Visual Studio Visual Studio projects"
3-
ms.date: "08/30/2019"
3+
ms.date: "06/02/2020"
44
ms.description: "Configure a Visual Studio MSBuild project to use the Clang/LLVM toolchain."
55
helpviewer_keywords: ["Clang support for C++ MSBuild projects"]
66
---
@@ -28,7 +28,7 @@ To configure a Visual Studio project to use Clang, right-click on the project no
2828

2929
![Clang component installation](media/clang-msbuild-prop-page.png)
3030

31-
If you are using the Clang tools that are bundled with Visual Studio, no additional steps are required. For Windows projects, Visual Studio by default invokes Clang in [clang-cl](https://llvm.org/devmtg/2014-04/PDFs/Talks/clang-cl.pdf) mode and links with the Microsoft implementation of the Standard Library. By default, **clang-cl.exe** is located in `C:\Program Files (x86)\Microsoft Visual Studio\2019\Common7\IDE\CommonExtensions\Microsoft\Llvm\bin`.
31+
If you are using the Clang tools that are bundled with Visual Studio, no additional steps are required. For Windows projects, Visual Studio by default invokes Clang in [clang-cl](https://llvm.org/devmtg/2014-04/PDFs/Talks/clang-cl.pdf) mode and links with the Microsoft implementation of the Standard Library. By default, **clang-cl.exe** is located in *%VCINSTALLDIR%\\Tools\\Llvm\\bin\\* and *%VCINSTALLDIR%\\Tools\\Llvm\\x64\\bin\\*.
3232

3333
If you are using a custom Clang installation, you can either modify **Project** > **Properties** > **VC++ DIrectories** > **Configuration Properties** > **Executable Directories** by adding the custom Clang installation root as the first directory there, or change the value of the `LLVMInstallDir` property. See [Set a custom LLVM location](#custom_llvm_location) for more information.
3434

0 commit comments

Comments
 (0)