>>106156995 (OP)you're just using cmake wrong
for some reason your source directory (where CMakeLists.txt is) is being prepended by your build directory (where the output goes)
if i had to guess quoting/escaping issue between windows quoting rules and mingw quoting rules, or it's because you're mixing build envs and using windows paths to some parameter being passed to a build tool that has to run under the MSYS2 cygwin based support runtime expects cygwin style "unix" paths
you conveniently covered up the actual invocation
>>106158523native (not built in or for mingw64 or MSYS2) windows binaries of the windows compatible llvm/clang toolchain (i.e. clang-cl) and the microsoft STL
support for 90% of gcc extensions on native windows as well as MS extensions
if they're in its repository, and they probably are, use vcpkg to install dependencies that have to be built by MSYS2/mingw (and just stuff in general) and it'll handle the mess
you shouldn't need mingw style POSIX support for new projects, it's mostly for building windows C ABI compatible versions of existing POSIX/linux projects
oh and use native windows cmake targeting ninja as a generator
the fuck are you using mingw/unix makefiles for
the only generator anyone uses regardless of platform is ninja and/or the newer ninja multi-config or occasionally msbuild if some fucky MSVC shit is needed
and clean up any detectable side affects MSYS2 left on your system, iirc cmake tries to detect things from it too often