Keqing Li

Hum... There is a switch in configure script that can choose which C runtime will be used via "--with-msvcrt=xxx". And I have the source code reconstructed by reverse engineering. It doesn't matter which C++ runtime I choose since the part I rewritten doesn't expose any C++ symbols and I can link libc++ statically.

Hum... There is a switch in configure script that can choose which C runtime will be used via "--with-msvcrt=xxx". And I have the source code reconstructed by reverse engineering. It doesn't matter which C++ runtime what I choose since the part I rewritten doesn't expose any C++ symbols and I can link libc++ statically.

I have a fantastic net game compiled by vs .net 2003 without source code, I'm working on build replicate parts to make it modern, but the game itself is relay on the shared msvcr71.dll and there're bunches of functions relay on C-style IO and memory management(such as FILE* and malloc, and C++ new and delete mechanism), so it will be a hell for me to make some parts linked with msvcrt or ucrt and others linked with the legacy msvcr71. So I tried to build a i386-targetted llvm-mingw toolchain with...