@@ -61,23 +61,19 @@ You can use the IDE to switch to clang-cl for local development,
6161but because this alters the *.vcxproj files, the recommended way is
6262to use build.bat:
6363
64- build.bat "/p:PlatformToolset=ClangCL" "/p:PreferredToolArchitecture=x64"
64+ build.bat "/p:PlatformToolset=ClangCL"
6565
6666All other build.bat options continue to work as with MSVC, so this
67- will create a 64bit release binary. PreferredToolArchitecture is needed,
68- because msbuild by default selects the 32bit architecture of the toolset,
69- which uses -m32 as the default target architecture.
67+ will create a 64bit release binary.
7068
7169You can also use a specific version of clang-cl downloaded from
7270https://github.com/llvm/llvm-project/releases, e.g.
7371clang+llvm-18.1.8-x86_64-pc-windows-msvc.tar.xz.
7472Given you have extracted that to <my-clang-dir>, you can use it like so
7573build.bat --pgo "/p:PlatformToolset=ClangCL" "/p:LLVMInstallDir=<my-clang-dir> "/p:LLVMToolsVersion=18"
7674
77- Here, PreferredToolArchitecture is not needed, because this is a 64bit
78- platform toolset, but LLVMToolsVersion has to be set accordingly.
79- Setting the major version is enough, although you can be specific
80- and use 18.1.8 in the above example, too.
75+ Setting LLVMToolsVersion to the major version is enough, although you
76+ can be specific and use 18.1.8 in the above example, too.
8177
8278Use the --pgo option to build with PGO (Profile Guided Optimization).
8379
0 commit comments