sykhro

You need to pass `--include-debug-libs` to xwin

The proper CMake way of doing this is using a toolchain file. [Here](https://github.com/llvm/llvm-project/blob/main/llvm/cmake/platforms/WinMsvc.cmake) is an example of how LLVM are using clang-cl it to (cross-)compile LLVM itself.

It's because of recursive submodules, see https://github.com/webfactory/ssh-agent/issues/130#issuecomment-1284043999 The workaround is to use the checkout action, init submodules manually, use this action, clone submodules manually.

+1 on documenting it.

This is the standard behaviour when using self-hosted runners with GitHub Actions. You are responsible for cleanup in your own workflows

> Please do not include toolchains from CMakeLists.txt. The toolchain must be passed externally with cmake ... -DCMAKE_TOOLCHAIN_FILE=....conan_toolchain.cmake. The behavior and the result is not the same. Thanks, noted. However,...

> ... the build scripts of fmt are more permissive and will build even for an unknown build_type? It may come as a surprise but so far the most random...

> With > > > conan install . -s:h "build_type=MyBuildType" -d full_deploy --deployer-folder=out --output-folder=out --build=missing -g CMakeToolchain -g CMakeDeps -c tools.cmake.cmaketoolchain:generator="Ninja Multi-Config" > > ``` > [vcvarsall.bat] Environment initialized for:...

It's most likely that`CMAKE_CONFIGURATION_TYPES` is not set correctly and CMake has generated `build-Release.ninja` and `build-Debug.ninja`. `thePlatform` toolchain file sets it; I didn't need to set it on Linux though (on...

> &:build_type=Debug Oh, I had no idea this was possible. What's the meaning this syntax? Is it aliasing `Debug` to `MyBuildType`? Does it create any conflicts with the actual `Debug`...