3 ms·
Well, we package our own software so we can work around any quirks that our system introduces, but actually generic cmake should work fairly well out of the box
by RayDonnelly 11y ago
Well, we package our own software so we can work around any quirks that our system introduces, but actually generic cmake should work fairly well out of the box.
The difference will the down to path translation. We don't stick to the old MSYS rules precisely as that code was re-written for MSYS2. MSYS2_ARG_CONV_EXCL can be used to prevent specific translations from happening too.
A bug report would be appreciated anyway.
- xaduha 11y agoSure, I'll make a bug report, should it go here? https://github.com/alexpux/mingw-packages https://github.com/alexpux/mingw-packages BTW thing that I was able to compile with old MSYS + cmake from cmake.org, but can't with MSYS2 and mingw-w64-i686-cmake is https://github.com/Absolight/pkcs11-proxy https://github.com/Absolight/pkcs11-proxy
- RayDonnelly 11y agoYeah, but you need to be clear that it wasn't our cmake build of course. Generally get used using, asking for and contributing to MSYS2 packages if you can. That way everyone benefits. It's not the norm on Windows, but it very much should be.