Mirror of forum.nim-lang.org

53 :: Unnecessarily unefficient cross compiling

• Schala (orginal) [2012-07-08T02:02:32+02:00] view original

  With support for ARM and thus embedded systems, I feel I must speak out. The current "cross compiler" needs to be reworked, and while I don't know the internals that well, I can imagine it wouldn't be that hard to change. A simple but efficient strategy would be to delegate the generated C/C++/ObjC code to a cross compiler toolchain (ie. i486-mingw32-gcc, which is Arch Linux's Linux-to-Win32 build of GCC or arm-wince-gcc which is a cross compiler to WinCE), much like non-cross-compiling delegates to system's compiler.

---

• Araq (orginal) [2012-07-08T10:56:24+02:00] view original

  Alright, I think we should do it this way: For cross compilation, the compiler invokes a C compiler named like $cpu.$os.$cc (for example arm.linux.gcc) and the configuration system is used to provide meaningful defaults. This means that the compiler doesn't stop compilation for cross compilation anymore and you need to pass --compileOnly to get back the old behaviour.

---

• Schala (orginal) [2012-07-08T11:08:27+02:00] view original

  Yes! Excellent! I think that indeed works!

---

• Araq (orginal) [2012-07-08T23:35:42+02:00] view original

  This has been implemented now.

---