Rockbox General > Rockbox General Discussion

Pre-built arm-elf-eabi-gcc cygwin binaries?

(1/2) > >>

karltpb:
Could someone provide the compiled binaries for the new arm cross compile tool chain with the appropriate patches applied? Running rockboxdev.sh consumes a lot of time on cygwin.

Compiled binaries would be awesome to have, much like those available of the older tool chain.

[Saint]:
There really are very few devs that use CygWin, I personally only know of 2.
It may take some time to compile the toolchains, but it's something you (should) only need to do once. Set it up to run overnight while you won't be using your machine for anything else and you won't even notice how long it takes.

Just set up CygWin with the packages it mentions on the wiki (not the toolchain packages though), don't forget to install curl while you're setting up CygWin (you can run the setup again and install it as well) because rockboxdev.sh requires this to download additional things it needs to compile the toolchain(s).

Make sure you have an up-to-date version of the Rockbox source code, cd to the "tools" directory, run rockboxdev.sh ("./rockboxdev.sh"), select the toolchain(s) you want to build, press enter and go to bed.

Wake up in the morning, done.

torne:
Very few of the developers use cygwin because it's slow (not just to build the toolchain, but to build Rockbox as well) and it introduces all kinds of possible complications (line endings, etc). We generally recommend that people use our Linux virtual machine image if they want to build on a Windows computer, rather than using Cygwin. See http://www.rockbox.org/wiki/VMwareDevelopmentPlatform

karltpb:
Thank you for your advice, guys. But I'm comfortable with cygwin as I use the same for other projects as well.

This may sound silly but, does someone who has built the new tool chain know how much temporary space is required to build them in cygwin?

And perhaps some way to remove the temporary data, because when I built the old tool chain it took more than a gig as opposed to a couple of hundred megabytes occupied by the pre-built packages.

Lear:
The (unpacked) source takes about 280 MB, and the intermediate files about 330 MB. That's size on disk for binutils and gcc.

After you've installed it, you can just delete the source and intermediate files.

Navigation

[0] Message Index

[#] Next page