Re:Building GCC as a Cross Compiler for Raspberry Pi
by blackflame7000 on Saturday May 12, 2018 @09:22AM
(#17053940)
I really wish I had read this a year ago when I was struggling with cross-compiling Qt for the RaspberryPi and instead natively built it which took 3 days.
[ Parent
| on HN ]
Re:Building GCC as a Cross Compiler for Raspberry Pi
by any1 on Saturday May 12, 2018 @11:10AM
(#17054386)
Well, I've actually spent 3 days trying to get Qt5 to cross-compile for a custom arm platform. It might be easier for something common like the raspberry pi, but still, you may have dodged a bullet there. ;)
The worst thing about cross-compiling Qt is that I always run into different issues with new releases, and it's not even always consistent between builds. I ended up renting a 64 core VPS to build Qt so that I could iterate faster though build failures, but it's still at least half a day's work to get it to build properly.
Re:Building GCC as a Cross Compiler for Raspberry Pi
by blackflame7000 on Saturday May 12, 2018 @12:17PM
(#17054725)
I hear ya, especially with respect to upgrades. Like without fail MYSQL Plugin will always be missing, QtWebsockets won't build automatically, and even now on ubuntu 18.04 which ships with openssl1.1.0 I discovered all my applications can no longer use https properly until I downgraded libssl to 1.0.2
Also: I'm assuming the 64 core machine is ARM? Which provider do you use for that?
Re:Building GCC as a Cross Compiler for Raspberry Pi
by any1 on Saturday May 12, 2018 @01:31PM
(#17055086)
I'm cross-compiling, meaning I'm not compiling on ARM. ;)
It might be helpful though for 64 bit ARM, but my target architecture is 32 bit and because I need webengine I suspect that it will not compile on a 32 bit platform. The problem is that the linker requires more memory than can be addressed in a 32 bit address space for linking chrome/webengine.
I just used google cloud.