I'm testing this toolchain, currently using it to target windows NT 4.0, using x-mingw32_486-msvcrt_win98-15.2.0-r7.tar.zst to build on CIs, and mingw32_486-msvcrt_win98-15.2.0-r7.7z to develop locally on windows.
I noticed that with the same build options, binaries compiled on windows import different libraries than the ones compiled by the CI.
After investigating, i noticed that the libraries shipped between the 2 packages are slightly different, libmsvcrt.a from the cross compiler contains the various thunks compiled in, while the one from the native toolchain lack them, thus resolving functions differently when linking (for example _wutime64 is thunked when cross compiling, but imported when compiling natively)
I'm testing this toolchain, currently using it to target windows NT 4.0, using
x-mingw32_486-msvcrt_win98-15.2.0-r7.tar.zstto build on CIs, andmingw32_486-msvcrt_win98-15.2.0-r7.7zto develop locally on windows.I noticed that with the same build options, binaries compiled on windows import different libraries than the ones compiled by the CI.
After investigating, i noticed that the libraries shipped between the 2 packages are slightly different,
libmsvcrt.afrom the cross compiler contains the various thunks compiled in, while the one from the native toolchain lack them, thus resolving functions differently when linking (for example_wutime64is thunked when cross compiling, but imported when compiling natively)