Changes between Initial Version and Version 1 of UsingIcecreamWithQtWebKit


Ignore:
Timestamp:
Nov 8, 2011 5:43:18 AM (11 years ago)
Author:
alexander.faeroy@nokia.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • UsingIcecreamWithQtWebKit

    v1 v1  
     1= Using Icecream with QtWebKit =
     2
     3This guide will help you through setting up the Icecream distributed
     4compilation suite on your Ubuntu workstation.
     5
     6This guide assumes that you are working in a heterogeneous build environment
     7where multiple people are running different versions of their distribution than the rest of the team.
     8
     9== Host Setup ==
     10
     11Start by installing the `icecc` package as `root`:
     12
     13{{{
     14$ apt-get install icecc
     15}}}
     16
     17If you are interested in monitoring your compilation jobs, you can also install
     18the `icemon` package.
     19
     20'''Note:''' If you want to trick your teammates into contributing to the
     21build-farm, well-knowing that they have no interest in using the build-farm
     22themselves, just convince them to install the `icecc` package and ensure that
     23the daemon is running on their machines.
     24
     25=== Scheduler ===
     26
     27One computer in your network will have to run a scheduler-daemon for the
     28build-farm. This does not have to be a fast machine and the scheduler can run
     29on a machine that participates in the compilation jobs as well.
     30
     31To start the scheduler during boot, open the `/etc/default/icecc` file and
     32ensure that the file contains the following:
     33
     34{{{
     35START_ICECC="true"
     36START_ICECC_SCHEDULER="true"
     37}}}
     38
     39Remember to restart the `icecc` service before the change will take effect:
     40
     41{{{
     42$ sudo /etc/init.d/icecc restart
     43}}}
     44
     45=== Using your Native Compiler on Remote Machines ===
     46
     47`icecc` supports using a packed down version of your local compiler on the other machines participating in the build-farm.
     48
     49To generate such package, run:
     50
     51{{{
     52$ icecc --build-native
     53}}}
     54
     55The `.tar.gz` file it generates has an MD5 sum as name and it is generally
     56considered to be a good idea to keep that name to avoid collisions when the
     57file is distributed out to your teammates computers.
     58
     59To make `icecc` your newly created package, run:
     60
     61{{{
     62$ export ICECC_VERSION="/path/to/md5sum.tar.gz"
     63}}}
     64
     65== Scratchbox Setup ==
     66
     67First of all, ensure that icecc is working correctly on your host setup before
     68you start trying to get it working in Scratchbox.
     69
     70== Caveats ==
     71
     72Here are my debugging hints that I used when I tried to get this up and
     73running.
     74
     75=== Getting Debug Output from `icecc` ===
     76
     77If you want to figure out what is going on with `icecc`, during builds, try the following:
     78
     79{{{
     80$ export ICECC_DEBUG="debug"
     81}}}
     82
     83This will make `icecc` write what it is currently doing and you will be able to
     84identify which compilers are being executed on the various machines in your
     85compilation cluster.