I've used mingw in the past, the exe usually is 10x the size and wants the entire binary of any library used as well and first requires you to download the source windows version of the lib and link it. Meaning a small SDL2 project on Linux was I think 100kib while on windows it was 1mib + 2.5 mib
Windows has dll hell... so basically, to ge around this, some tools statically link by default. It's not an ideal solution, but it works most of the time... and regarding how unmainatained a Windows install might be (old installs, like Win7) or how badly updated/upgraded it might be (newer installs, Win10 and 11), I guess it is the only choice you actually have to make your app run on as many Windows systems as possible.
Do it the long way and compile in a vm.
My thoughts exactly... seems to be the safest route.
Best I can do is make an elf that mostly works and the memory manager seems pretty solid but the second you start doing stuff with strings, it fucks all up and I never figured out that bug after months so it is what it is. If you want to print a string you have to drop into real mode first.
I was able to use this guys docker image and tool in order to cross compile my Rust programs in the past. They were very simple programs so I dont know how well it works for larger projects.
You could even cross-compile from musl... very cool ๐!
I heard recently that you can use the zig compiler to cross compile rust programs.
Is it's C, you could use Cosmopolitan
No, it's Vala... and it's not my project, client just wants this to run on Windows.
Simply install Ubuntu from Microsoft Store.
They should just use reverse-wine, if that exists.
Wish it did...
