3 ms·
Nim always relies on an underlying platform compiler. Getting an .o out from a cross compiler is easy, in my experience - the big problem is getting libraries,
by beagle3 6y ago
Nim always relies on an underlying platform compiler.
Getting an .o out from a cross compiler is easy, in my experience - the big problem is getting libraries, includes and linkage right. And in my (admittedly small) experience, Nim makes that part much simpler as soon as you have a compiler set up (which in my case was an apt-get away)
- sim_card_map 6y agoYeah it's nice when it's an apt install away. Not so nice on Windows or macOS. While Go supports it all out of the box.
- beagle3 6y agoBut do note the apt-get doesn’t get you far. You now have a compiler that can produce .o, but headers, libraries, borked make files that are unaware of cross compiles etc are still a problem. Not so with Nim.