...

Note: just like in Unix, adding to the path doesn’t refresh active terminals. You’ll need to open a fresh one/google the “source ~/.bashrc” equivalent for Windows.

After following this guide your PATH should have these extra entries:

• C:\Users\tcwg\AppData\Local\Programs\Python\Python39-32\Scripts\

• C:\Users\tcwg\AppData\Local\Programs\Python\Python39-32\

• C:\Program Files (x86)\Git\usr\bin

  • This is for mingw utilities. Git adds itself to System PATH

• C:\Users\tcwg\source\ninja

• C:\Program Files\LLVM\bin

• C:\Program Files (x86)\CMake\bin

For building release packages we also install 7-Zip https://www.7-zip.org/download.html and NSIS https://nsis.sourceforge.io/Download

• C:\Program Files (x86)\7-Zip

• C:\Program Files (x86)\NSIS

Install Visual Studio Build Tools

...

• MSVC v142 - VS 2019 C++ x64/x86 build tools (latest)

  • This is needed to make vsdevcmd.bat correctly setup LIB/LIBPATH/INCLUDE variables for x86->arm64 cross-compilation. All the lib/header files are actually present, but vsdevcmd.bat doesn’t add them without x86-hosted tools.

  • Installing this may become optional in the future

• MSVC v142 - VS 2019 C++ ARM64 build tools (latest)

  • Without these vsdecmd.bat doesn’t setup x86->arm64 cross-compilation.

• C++ ATL for latest v142 build tools (ARM64)

  • LLVM uses ATL libraries

• Windows 10 SDK

  • Versions … 18362 and 19041 are known to work

  • Version 20348 is known to cause LLVM build failure

    • error: use of undeclared identifier '__umulh'

  • This is required for correct cross-compilation setup. Not sure if SDK libraries are actually used

...