it's wild that native toolchains use something called "triple" that consists out of four parts
-
it's just that, like, I don't feel like there's any fundamental reason for them to cause as much suffering as they invariably cause
As someone who has worked in embedded and is currently working on RISC-V I have to disagree vehemently. Also: Most of the troubles with cross compilers have nothing to do with the compilers but with libraries and stuff like lib paths. Fuck those! -ffreestanding -nostdlib :)
-
-
this doesn't work very well if you're writing C++!
-
Most of my cross GCCs are built with --enable-languages=c anyway. But I can see your point.
End of conversation
New conversation -
-
-
I don't find that they cause much suffering unless people expect to just pull in random dependencies from all over (eg, packages installed on their build machine, rather than third-party code vendored into their source tree). If you manage your whole build tree, life is saner.
-
Mind you, it's work, but it's worth it. Some of this comes from a background of building-the-whole-OS and wanting or needing to know where exactly every bit of source comes from and keep track of it. YMMV, I suppose.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.