1,502
edits
Difference between revisions of "Buildbot"
Wrap all the console commands inside source tags
(→Administration: Add HOWTO on building libraries for toolchains on Buildbot.) |
(Wrap all the console commands inside source tags) |
||
| Line 51: | Line 51: | ||
When the buildbot config files are changed, a user with shell access and sudo privileges needs to run the following commands. It's good practice to do this once buildbot is idle: | When the buildbot config files are changed, a user with shell access and sudo privileges needs to run the following commands. It's good practice to do this once buildbot is idle: | ||
<source lang="bash"> | |||
sudo -s | |||
/etc/init.d/buildslave stop | |||
/etc/init.d/buildbot stop | |||
cd ~buildbot/buildbot | |||
git pull | |||
/etc/init.d/buildbot start | |||
/etc/init.d/buildslave start | |||
</source> | |||
If problems arise, check if all files in the master (~buildbot/master) and slave (~buildbot/slave) directories are owned by the correct user (buildbot:nogroup). If the daemons were incorrectly started, new files might have been created under another user account. In that case: | If problems arise, check if all files in the master (~buildbot/master) and slave (~buildbot/slave) directories are owned by the correct user (buildbot:nogroup). If the daemons were incorrectly started, new files might have been created under another user account. In that case: | ||
| Line 63: | Line 65: | ||
* stop the daemons (see above) | * stop the daemons (see above) | ||
* fix the permissions with | * fix the permissions with | ||
<source lang="bash"> | |||
chown -R buildbot:nogroup ~buildbot/master/* | |||
chown -R buildbot:nogroup ~buildbot/slave/* | |||
</source> | |||
* start the daemons | * start the daemons | ||
| Line 94: | Line 98: | ||
* Decompress the latest libSDL tarball to a temporary location i.e. | * Decompress the latest libSDL tarball to a temporary location i.e. | ||
<source lang="bash"> | |||
tar -xvzf SDL-1.2.15.tar.gz -d /home/digitall | |||
</source> | |||
* Apply any required patches i.e. Currently libSDL-1.2.15 snapshot has a error in the Win32 version strings.. This may occur again on future releases :/ | * Apply any required patches i.e. Currently libSDL-1.2.15 snapshot has a error in the Win32 version strings.. This may occur again on future releases :/ | ||
<source lang="bash"> | |||
patch -p0 < SDL-1.2.15-Fix-Windows-DLL-Version.patch | |||
</source> | |||
* Add toolchain binaries directory to path. | * Add toolchain binaries directory to path. | ||
<source lang="bash"> | |||
PATH=/opt/toolchains/x86_64-w64-mingw32/bin:$PATH | |||
export PATH | |||
</source> | |||
* Add out of tree build directory and configure the SDL codebase here with the host target and prefix to use the correct cross toolchain and target for make install. | * Add out of tree build directory and configure the SDL codebase here with the host target and prefix to use the correct cross toolchain and target for make install. | ||
<source lang="bash"> | |||
mkdir SDL-1.2.15-x86_64-w64-mingw32 | |||
cd SDL-1.2.15-x86_64-w64-mingw32 | |||
../SDL-1.2.15/configure --host=x86_64-w64-mingw32 --prefix=/opt/toolchains/x86_64-w64-mingw32 | |||
</source> | |||
* Compile the codebase. | * Compile the codebase. | ||
<source lang="bash"> | |||
make | |||
</source> | |||
* Install the compiled files. As you become root, you need to make the same modification to the path to get the required cross toolchain tools such as ranlib. | * Install the compiled files. As you become root, you need to make the same modification to the path to get the required cross toolchain tools such as ranlib. | ||
<source lang="bash"> | |||
sudo bash | |||
PATH=/opt/toolchains/x86_64-w64-mingw32/bin:$PATH | |||
export PATH | |||
make install | |||
</source> | |||