From the homepage at http://distcc.samba.org/, "distcc is a program to distribute builds of C, C++, Objective C or Objective C++ code across several machines on a network. distcc should always generate the same results as a local build, is simple to install and use, and is usually much faster than a local compile."
In theory, distcc should allow you to speed up native builds on the slug dramatically by using other machines on your network. In practice, its use is a bit finicky unless it's set up just right.
In order to make using distcc, you need to feed the
That should be it! As always, correct with wiki if you find any tricks or pitfalls to this process.
On my PC, with optware/nslu2/toolchain built, I did the following:
$ cd ~/slug/optware/nslu2/toolchain/armv5b-softfloat-linux/gcc-3.3.5-glibc-2.2.5/armv5b-softfloat-linux/bin $ ln -s gcc cc $ cd ~/slug/optware/nslu2 $ mkdir distcc && cd distcc $ vi distccd.sh NSLU2_HOME=$HOME/slug/optware/nslu2 PATH=$NSLU2_HOME/toolchain/armv5b-softfloat-linux/gcc-3.3.5-glibc-2.2.5/armv5b-softfloat-linux/bin:$PATH \ distccd --daemon --allow 192.168.1.0/24 --log-file=$NSLU2_HOME/distcc/distccd.log $ chmod +x distccd.sh $ ./distccd.sh
On my slug, I can then do
On my PC, with slugosbe toolchain built (see SlugosbeDevel), I did the following:
$ cd ~/slug/slugosbe/tmp/cross/armeb-linux/bin && ln -s gcc cc $ cd ~/slug/optware/slugosbe $ mkdir -p distcc && cd distcc $ vi distccd.sh PATH=~/slug/slugosbe/tmp/cross/armeb-linux/bin:$PATH \ distccd --daemon -p 3633 --allow 192.168.1.0/24 --log-file=~/slug/optware/slugosbe/distcc/distccd.log $ chmod +x distccd.sh $ ./distccd.sh
On my slugosbe slug, I can then do