On 2026/09/03 02:26, Pali Rohár wrote: > liblargeint.a is also for MSVC compatibility. Older versions provided > static largeint.lib library which applications could statically link.
Do we really need to provide this type of "compatiblity"? Searching GitHub for "-llargeint" [1] matches only 10 code snippet, which I think is rare enough for us to no longer provide it. Searching for "liblargeint.a" [2] matches 0 real usage. For other potential usage of it (e.g. largeint.lib), they always have to be patched before use, and there's little difference between patching 'largeint.lib' to '-llargeint' or simply removing it. The similar logic also applies to libdelayimp.a, though this is a little more complicated (or confusing), because people may expect this is required if they want to use "delay import", which is a relatively new feature compared to largeint. And indeed there're more usage of `-ldelayimp` on GitHub (~200), though many of them seemes to be intended for MSVC (either explicitly specifies "NOT VCPKG_TARGET_IS_MINGW", or used with "/DELAYLOAD:", or searching from Windows Kits explicitly.) [1]: https://github.com/search?q=-llargeint&type=code [2]: https://github.com/search?q=liblargeint.a&type=code _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
