Travis CI Continuous Integration system - for users with Github repos

[whiskers75]

I have managed to get (very unstable) Travis working with Rockbox.
(about.travis-ci.org)
If anyone wants my .travis.yml file, they can have it. Get it from whiskers75/rockbox (https://github.com/whiskers75/rockbox/blob/master/.travis.yml).
Currently builds Sansa Clip+ and iPod Mini 1G. (62 and 25)
If anyone can provide 32-bit Ubuntu 12.04 toolchain packages, that would be greatly appreciated and fix all the problems I have with Travis.
Good day,
whiskers75

[[Saint]]

rockboxdev.sh is perfectly capable of compiling the toolchains.

However, it assumes that your environment is actually capable of compiling the toolchains (ie. meeting dependencies). For everything except the YP-R0 toolchain, these dependencies are very simply met (and documented).

From a clean install, only these packages should be needed:

Code: [Select]

build-essential libc6-dev libgmp3-dev libmpfr-dev texinfo

There are a few packages that will be used if present, but are not needed (bison, CLooG, flex, ...the list goes on).

My guess is that instead of looking at the error the toolchain compilation failed with (which will always be your clue as to why it failed), you've assumed it is broken and stopped there. It does work, though. If you are unable to work out why compilation is failing for you, posting the error from the output is infinitely more helpful that simple saying "It's buggy" (simplification taken from another post).


[Saint]

[whiskers75]

Travis has a stupid timeout of 10 minutes per command, so I can't use rockobxdev.sh. Sometimes make takes too long so my build fails - that's why I need some APT packages for 32-bit Ubuntu Server 12.04.

[[Saint]]

So....stop using it. From what I've seen it is basically useless anyway. Telling if your code compiles or not, as you've seen, doesn't actually give any indication as to whether or not it is going to work.


[Saint]

[wodz]

You are most probably not aware of this: http://build.rockbox.org/dev.cgi. We are pretty sure that our codebase compiles (mostly) cleanly with advised toolchains. There is little point to check this. If you modify sources you have to compile it anyway to test so why bother with some external tools?

[whiskers75]

I am very much aware of that.