1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166
|
# Setting up buildmaster
The build master is set up using virtualenv, so that buildbot needs not to be installed as root, and so that buildbot can't conflict with other installed python packages.
So, first, set up the virtualenv (in the directory virtualenv in this example):
apt-get install python-dev python-virtualenv
virtualenv --no-site-packages virtualenv
echo 'source $HOME/virtualenv/bin/activate' >> ~/.profile
source virtualenv/bin/activate
Then we check out buildbot sources, switch to the last stable release, and install into the virtual environment.
git clone git://github.com/buildbot/buildbot.git
cd buildbot/master
git checkout v0.8.5
python setup.py install
After this commands like `buildbot create-master` and `buildbot start` can be used to create/control the master.
After creating the master, the generated `public_html` can be erased and linked to the `buildbot/master/public_html` in the Spring repository.
# Setting up buildslave (Making the chroot)
At least debootstrap and schroot are required. I didn't compile an exhaustive list of other dependencies on the host system, so YMMV.
## Configuring schroot
Add a file (name does not matter) to `/etc/schroot/chroot.d` with the following contents, after substituting an absolute path for `$DIR`:
[buildbot-maverick]
description=Ubuntu Maverick
directory=$DIR
type=directory
users=buildbot
groups=buildbot
root-groups=root
personality=linux32
script-config=script-defaults
message-verbosity=verbose
Then, remove or comment out the `/home` bind mount in `/etc/schroot/default/fstab`!
This configuration has been tested with schroot 1.4.23. With any other version YMMV.
## Building and entering the chroot
debootstrap --variant=buildd --arch i386 maverick $DIR http://ftp.cvut.cz/ubuntu/
mkdir -p $DIR/home/buildbot/www
chown buildbot:buildbot $DIR/home/buildbot
schroot -c buildbot-maverick
# Inside the chroot
## Run (as root)
echo 'deb http://ftp.cvut.cz/ubuntu maverick universe' >> /etc/apt/sources.list
sed s/deb/deb-src/g /etc/apt/sources.list >> /etc/apt/sources.list
apt-get update
apt-get install nano git-core python-dev python-setuptools
cd /root
git clone git://github.com/buildbot/buildbot.git
cd buildbot
git checkout v0.8.3p1
cd slave
python setup.py install
mkdir /slave
chown buildbot:buildbot /slave
Build dependencies for Windows build (except MinGW, see below):
apt-get install cmake nsis p7zip-full unzip wget pandoc
apt-get install openjdk-6-jdk #to enable building of Java AIs
Build dependencies for Linux build:
apt-get install libboost-all-dev libdevil-dev libfreetype6-dev libopenal-dev \
libogg-dev libvorbis-dev libglew-dev libsdl-dev libxcursor-dev \
cppcheck
## Recompile MinGW package with dwarf2 exceptions instead of sjlj exceptions (as root)
First recompile the compiler itself:
mkdir mingw
cd mingw
apt-get build-dep gcc-mingw32
apt-get source gcc-mingw32
cd gcc-mingw32-4.4.4
editor debian/rules # remove --enable-sjlj-exceptions, add --disable-sjlj-exceptions --with-dwarf2
dpkg-buildpackage -rfakeroot -b
cd ..
dpkg -i gcc-mingw32*.deb
echo "gcc-mingw32 hold"|dpkg --set-selections
Then recompile the runtime libraries against the new compiler:
apt-get build-dep mingw32-runtime
apt-get source mingw32-runtime
cd mingw32-runtime-3.15.2
dpkg-buildpackage -rfakeroot -b
cd ..
dpkg -i mingw32-runtime*.deb
echo "mingw32-runtime hold"|dpkg --set-selections
Optionally, remove build dependencies (check what apt-get build-dep installed!):
apt-get purge autoconf automake autotools-dev cdbs debhelper fdupes gettext \
gettext-base groff-base html2text intltool intltool-debian libcroco3 \
libfont-afm-perl libgmp3-dev libgmpxx4ldbl libhtml-format-perl \
libhtml-parser-perl libhtml-tagset-perl libhtml-tree-perl \
libmail-sendmail-perl libmailtools-perl libmpfr-dev \
libsys-hostname-long-perl libunistring0 liburi-perl libwww-perl \
libxml-parser-perl lzma m4 man-db mingw-w64 po-debconf
## Patch a few things
We set up ld to allow only one execution at the same time, to prevent thrashing the box due to multiple parallel linker jobs.
We "patch" makensis to not sync the installer to disk after every tiny chunk of data it has written.
This speeds installer building up by an order of magnitude.
First, copy over ld, makensis and no-msync.c from spring/buildbot/slave (Spring repository) to the chroot.
Then switch to the directory (inside the chroot!) where you copied those files and do:
For Linux builds:
mv /usr/bin/ld /usr/bin/ld.orig
cp ld /usr/bin/ld
For MinGW builds:
mv /usr/bin/i586-mingw32msvc-ld /usr/bin/i586-mingw32msvc-ld.orig
cp ld /usr/bin/i586-mingw32msvc-ld
mv /usr/i586-mingw32msvc/bin/ld /usr/i586-mingw32msvc/bin/ld.orig
cp ld /usr/i586-mingw32msvc/bin/ld
For makensis:
gcc -shared -m32 no-msync.c -o no-msync.so
cp makensis no-msync.so /usr/local/bin/
## Run (as buildbot user)
Substitute MASTER with host:port of the buildmaster and SLAVENAME and PASSWORD with the slave name and password as configured in the master.
buildslave create-slave /slave MASTER SLAVENAME PASSWORD
cd /slave
git clone git://github.com/spring/mingwlibs.git
## ccache
To install ccache simply run `apt-get install ccache` (inside the chroot) and (optionally) tweak the settings (cache size etc.)
# Outside the chroot again
Get the Makefile from the Spring repository that can be used to start/stop the slave easily:
wget https://raw.github.com/spring/spring/master/buildbot/master/buildbot.mk -O Makefile
Then you can use:
make start-slave # creates schroot session and starts buildslave in it
make stop-slave # stops buildslave and remove schroot session
make enter-chroot # enter the schroot as buildbot user
Make sure you review the Makefile and fix the chroot name, paths, etc. before using it!
(That applies to anything in this readme really.)
|