Prebuilt binary for Windows

I was referring to this: https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows. Granted, it was probably marked as non-critical, so some users may have skipped it.

One of the redist options is to include an MSU in your installer that tells Windows Update to add UCRT to the list of components it updates

We should figure out how to do that.

But meanwhile, do people here agree that LLVM should be built with the /MD flag?

I was referring to this: https://support.microsoft.com/en-us/help/
2999226/update-for-universal-c-runtime-in-windows. Granted, it was
probably marked as non-critical, so some users may have skipped it.

> One of the redist options is to include an MSU in your installer that
tells Windows Update to add UCRT to the list of components it updates

We should figure out how to do that.

But meanwhile, do people here agree that LLVM should be built with the /MD
flag?

Like Reid said above, clang should statically link the CRT.

We should do whatever makes it really simple to add clang to path and run
it without any DLL conflicts. If it's easy to copy the vc runtime DLLs into
our package in a compatible way, great, so long as users can unzip the
package and run it from whereever it is without installing any
dependencies. Static linking just happens to be the easiest way to achieve
that.

I don’t know an easy way to accomplish that. While app-local deployment is now supported, the set of deployed dlls depends on the host OS version (according to this). I’ve opened a bug for now.