spdlog VS cmake-init-clang-on-windows

Platform dependence: They seem to involve bizarrely low-level and compiler-specific details. Just look at this from the spdlog recipe:

Or LLVM Clang directly without a pseudo *nix environment: https://github.com/friendlyanon/cmake-init-clang-on-windows

While not embedded, but here is an example for compiling with LLVM Clang on Windows without needing vcvarsall.

I was informed that this is not the case. lld supports PE/COFF natively on Windows. You just need to provide some flags to use the MSVC .lib and include files to use Clang properly. Or use the vcvarsall, but that's stinky and I don't like having all that env stuff in my terminal all the time.

Regarding building, I'd advise staying as far away from Mingw, msys and Cygwin as possible. You can just use LLVM Clang without any issue on Windows. You can keep using vim with Clang tools as if you were on Linux still.

CMake, Clang and Conan work all the same on all operating systems. I don't know why you would like to force yourself into one kind of environment that might not suit your needs in other areas as well. On Windows, you can even use LLVM Clang without godawful hacks like mingw.

From a quick searching I found what it takes to compile a Windows executable on macOS, these flags could be very easily turned into a toolchain file and the situation would be similar on Linux as well.

cmake-init was just for a general project setup. One of the examples in fact shows what a toolchain file should look like.

You can also just use LLVM Clang on Windows. Still requires MSVC installed though, because of link.exe, system .libs and system headers.