I am attempting to follow this guide in setting up the Gentoo Buildbot:
http://springrts.com/wiki/Buildbot:Gent ... uildbot.29
I have successfully set up my Gentoo system, and completed all sections prior to "build Spring + dependencies in MinGW"
Within that section I completed "USE="minizip" emerge-i686-mingw32 sys-libs/zlib" successfully.
In the section 1. USE="static"
I am trying to execute:
emerge-i686-mingw32 app-arch/bzip2
Build log: http://gw.gd/K0LR
emerge --info: http://gw.gd/C9lB
emerge -pqv: http://gw.gd/dHsk
I don't quite know where to go from here. I do not have much experience working with the gentoo emerge system.
An Adventure in setting up the Gentoo Buildbot
Moderator: Moderators
Re: An Adventure in setting up the Gentoo Buildbot
oops, you're lucky, this step isn't required as all the libs for mingw32 cross compile are in mingwlibs: https://github.com/spring/mingwlibs
your mingw32 buildslave should be ready to compile!
(removed that part from the wiki)
i guess it was a start off, to compile some libs static...
your mingw32 buildslave should be ready to compile!
(removed that part from the wiki)
i guess it was a start off, to compile some libs static...
Re: An Adventure in setting up the Gentoo Buildbot
i still don't know what you want to do... so this time i guess what you maybe are trying to do:
if you want to extend the validation test, you don't need to setup a full buildbot setup. all buildsteps are shell scripts which are in buildbot/slave/validation in the source directory. tests-prepare.sh downloads needed files & creates startup scripts. the scripts are in most parts verbose and print which directories they use, so this should help.
when in the source-directory it should be possible to run it directly by
thats not fully tested, but should work...
CAUTION! please use a username with restricted access, as some cleanup script could do a rm -rf / script if some env var is unset. (this shouldn't happen, i added rm commands with care / at least a prefix so it doesn't delete to much, but who knows...)
if you want to write your own test scripts in lua, you've to create a mission or a game. easiest would be to create a svn repository (i heavily suggest github) & ask det to add it to rapid. then i can add it to the validation test and it can be automaticly run on the existing buildslave setup.
if you want to add tests to c++, then please use "make test" (see https://github.com/spring/spring/tree/develop/test )
if you want to extend the validation test, you don't need to setup a full buildbot setup. all buildsteps are shell scripts which are in buildbot/slave/validation in the source directory. tests-prepare.sh downloads needed files & creates startup scripts. the scripts are in most parts verbose and print which directories they use, so this should help.
when in the source-directory it should be possible to run it directly by
Code: Select all
buildbot/slave/create-build-dirs.sh default develop
buildbot/slave/validation/tests-prepare.sh default develop
buildbot/slave/validation/tests-run.sh default develop
CAUTION! please use a username with restricted access, as some cleanup script could do a rm -rf / script if some env var is unset. (this shouldn't happen, i added rm commands with care / at least a prefix so it doesn't delete to much, but who knows...)
if you want to write your own test scripts in lua, you've to create a mission or a game. easiest would be to create a svn repository (i heavily suggest github) & ask det to add it to rapid. then i can add it to the validation test and it can be automaticly run on the existing buildslave setup.
if you want to add tests to c++, then please use "make test" (see https://github.com/spring/spring/tree/develop/test )