Crosscompile the crosscompiler about bleeding-edge-toolchain HOT 5 CLOSED

BTW:

Needless to say, it takes quite some time

If you want to speed things up, be sure to use --skip-documentation --skip-nano-libraries - this will be ~2x faster than the regular build (and also a bit smaller).

from bleeding-edge-toolchain.

Well, the script is done in a way that it first builds the "native" compiler, then tries to cross-compile one for Windows. I guess that the part which does the "native" build has some hard-coded stuff which is not working properly when you try to force it to actually do a cross-compilation. So maybe it would be easier if you would try to modify the part of the script which actually cross-compiles the toolchain for Windows, to just do it for RPi? This would require some more steps than just changing the prefix from the one used by MinGW-W64 to your RPi toolchain, but would be probably doable. There are some differences in the build procedure itself, which are Windows-specific - for example building of libiconv, two versions of gdb, extracting python for windows and so on...

Another approach would be to find the parts which are forcing the build to be "native", which I guess would be at least these:

buildGmp ${buildNative} "" "--build=${hostTriplet} --host=${hostTriplet}"

For a cross build you need to have them different, not the same, for example see this line for Windows:

	buildGmp \
		${buildFolder} \
		${bannerPrefix} \
		"--build=${hostTriplet} --host=${triplet}"

Anyway - forcing the "native" part to do the cross-compilation would be hard, at least because the cross-compiler for ARM really needs to be run on the build machine, to compile the target libraries. That's why it would probably be much easier to modify the part which cross-compiles for Windows to do it for RPi.

from bleeding-edge-toolchain.

Thanks for the tip, I'll try the windows->rpi path.

Anyway - forcing the "native" part to do the cross-compilation would be hard, at least because the cross-compiler for ARM really needs to be run on the build machine, to compile the target libraries.

Yeah - I spent some time today realizing what you meant, the hard way. ;)

Again, thanks! I'll give it a go. You may close this issue if you want to - I'll post my findings here if I come up with something useful.

from bleeding-edge-toolchain.

As you wish (; Let me know if you face some other problems or just ask if something is not clear!

from bleeding-edge-toolchain.

If you want to speed things up, be sure to use --skip-documentation --skip-nano-libraries - this will be ~2x faster than the regular build (and also a bit smaller).

Trimming gcc/config/arm/t-rmprofile also helps a lot.

from bleeding-edge-toolchain.