Smacked head-first into a stupid issue with the #libcurl package deployed by #MinGW / #MSYS / #MinGW64 - turns out that if you copy the DLLs out of the MinGW environment (you know, like if you want to actually *deploy* an application that uses them), libcurl suddenly starts freaking out about "SSL CA cert" problems.

Someone on StackOverflow noticed there's an alternate "mingw-w64-x86_64-curl-winssl" package that doesn't seem to suffer from this issue (which I confirmed). What a damned mess!

How good is #msys these days? The occasional times I have to use #windows for #nextest are so frustrating. cmd sucks, git bash is too basic for me.

Pretty sure #MSYS #MinGW's 64-bit #libSDL 1.2 packages are also broken, as I get linker errors with libSDL_image.a and libSDL_mixer.a.

Meanwhile, Vcpkg doesn't have a full set of SDL 1.2 packages.

Not sure it's worth building every #OpenXcom dependency from source.

#xp

The version of #yaml-cpp currently shipped by #MSYS for #MinGW64 has a bug that prevents exporting a symbol to the shipped DLL. It's not MSYS' fault, because yaml-cpp hasn't put out an updated formal release since 10 months before fixing this: https://github.com/jbeder/yaml-cpp/issues/1026#issuecomment-1122305522

#xp

Trying to get #OpenXcom to build in #MSYS #MinGW64 using #CMake and #vscode, and of course it's a dumpster fire. *sigh*

It builds but barfs up a massive series of linker errors at the end, even though I already found and fixed one CMakeLists.txt issue. Whee!

#xp