Buildbot?
Moderator: Moderators
Re: Buildbot?
Does it make working compiles again now? Sorry, been away from this issue for a week, thought I'd check and see whether Bibim's gotten it running again. Sorry in advance for nagging, I'd like to test the new soundcode thoroughly soonish.
Re: Buildbot?
it kinda works, but is very picky wrt missing content, it seems. try any build with 'tdm' in the name.
also, when rebuilding, do !rebuild toolchain=tdm.
edit: it was a base file issue after all. the most recent builds should work fine.
also, when rebuilding, do !rebuild toolchain=tdm.
edit: it was a base file issue after all. the most recent builds should work fine.
Re: Buildbot?
Rebuilding now. Tried the latest TDM version, and had no sound other than the OGG files (which played but skipped a lot).
Re: Buildbot?
To clarify latest BuildServ changes concerning !rebuild command:
The "sys" parameter has been replaced by the "toolchain" (alias: "tc") parameter, so that it's possible to have multiple toolchains for same target system. Possible values for toolchain parameter are:
Finally, "tdm" is now the default toolchain.
The "sys" parameter has been replaced by the "toolchain" (alias: "tc") parameter, so that it's possible to have multiple toolchains for same target system. Possible values for toolchain parameter are:
- "native" --> gcc 4.3.2 (Debian Lenny native GCC)
- "mingw32" --> gcc 4.2.1-sjlj (Debian Lenny mingw32 GCC)
- "mingw64" --> gcc 4.4.0 experimental (Latest mingw-w64 project GCC)
- "tdm" --> gcc 4.3.2 (Latest Twilight Dragon Media GCC with MinGW)
Finally, "tdm" is now the default toolchain.
Re: Buildbot?
Updates for gcc 4.4.0:
Mingwlibs have been updated to v19 (v19_dwarf2 for "mingw32" only)
Possible values for toolchain parameter are:
Mingwlibs have been updated to v19 (v19_dwarf2 for "mingw32" only)
Possible values for toolchain parameter are:
- "native" --> gcc 4.3.3 (Debian Lenny native GCC)
- "mingw32" --> gcc 4.4.0 (Latest official mingw GCC)
- "mingw32_4.2.1" --> gcc 4.2.1-sjlj (Debian Lenny mingw GCC)
- "mingw64" --> gcc 4.4.0 (Latest official mingw64 GCC)
- "tdm" --> gcc 4.4.0 (Latest Twilight Dragon Media GCC)
- "tdm433" --> gcc 4.3.3 (Twilight Dragon Media GCC 4.3.3)
- "tdm432" --> gcc 4.3.2 (Twilight Dragon Media GCC 4.3.2)
Re: Buildbot?
My ISP no longer lets me store data for free on planetspring.free.fr, so currently BuildServ builds are no longer available online...
If anyone can offer a stable hosting to replace planetspring, it could be really usefull. BuildServ binaries and debug symbols should take less than 10GB (old ones are removed), and they are uploaded through FTP.
These binaries are used mainly by developers and testers, so the traffic shoudn't be very big.
If anyone can offer a stable hosting to replace planetspring, it could be really usefull. BuildServ binaries and debug symbols should take less than 10GB (old ones are removed), and they are uploaded through FTP.
These binaries are used mainly by developers and testers, so the traffic shoudn't be very big.
Re: Buildbot?
So, you just need FTP access to a directory, and 10GB of storage? I can probably do that.
Re: Buildbot?
Thank you Argh.
Actually I just re-configured BuildServ to use this site http://buildbot.eat-peet.net/spring/, provided by Peet.
We'll see how it goes, but for now it seems to be ok, so thank you Peet!
Actually I just re-configured BuildServ to use this site http://buildbot.eat-peet.net/spring/, provided by Peet.
We'll see how it goes, but for now it seems to be ok, so thank you Peet!
Re: Buildbot?
Ill offer you an arbitrary amount of your choosing (upto 1TB) with php mysql ruby basic shell ( no java/bg processes ), and good bandwidth (download anything from the JJ darkstars mirror to see )