Icecream Scratchbox Howto - Revision history

imported_>lizardo: /* Prerequisites */

2010-02-10T12:27:59Z

Prerequisites

← Older revision		Revision as of 12:27, 10 February 2010
Line 34:		Line 34:
	export ICECC_VERSION=$icecc_tarball		export ICECC_VERSION=$icecc_tarball
	export PATH=/usr/lib/icecc/bin:$PATH		export PATH=/usr/lib/icecc/bin:$PATH
	export ~~MAKEFLAGS~~=~~-j12~~		export DEB_BUILD_OPTIONS=$DEB_BUILD_OPTIONS,parallel=12
	fi		fi
	unset icecc_tarball procfamily DISTRIB_ID DISTRIB_RELEASE DISTRIB_CODENAME DISTRIB_DESCRIPTION		unset icecc_tarball procfamily DISTRIB_ID DISTRIB_RELEASE DISTRIB_CODENAME DISTRIB_DESCRIPTION
Line 40:		Line 40:

	Note that on other distributions than Ubuntu, you might have to modify this, depending on the contents on /etc/lsb-release.		Note that on other distributions than Ubuntu, you might have to modify this, depending on the contents on /etc/lsb-release.

			Also note the "parallel=N" parameter being added to DEB_BUILD_OPTIONS. This enables parallel builds (limited to N parallel jobs) for those packages that support it. Alternatively, if you are doing your own builds by calling "make", you should instead pass the "-jN" parameter to enable parallel builds, e.g. "make -j12".

	Then, create directory $HOME/icecc and run <pre>icecc --build-native</pre> there. Symlink the created tarball to a descriptive name, e.g. icecc-i686-karmic.tar.gz (this name has to match the $icecc_tarball variable in the .bashrc snippet above).		Then, create directory $HOME/icecc and run <pre>icecc --build-native</pre> there. Symlink the created tarball to a descriptive name, e.g. icecc-i686-karmic.tar.gz (this name has to match the $icecc_tarball variable in the .bashrc snippet above).

imported_>mairas: /* Using icecc */

2010-02-10T07:36:20Z

Using icecc

← Older revision		Revision as of 07:36, 10 February 2010
Line 122:		Line 122:
	sbox_compiler="$(sb-conf show --compiler)"		sbox_compiler="$(sb-conf show --compiler)"
	# use the tarball name with the MD5, avoiding conflicting names in peer caches		# use the tarball name with the MD5, avoiding conflicting names in peer caches
	icecc_tarball="$(readlink -f $HOME/icecc_sbox-$sbox_compiler.tar.gz)"		icecc_tarball="$(readlink -f $HOME/icecc/icecc_sbox-$sbox_compiler.tar.gz)"
	if [ -f "$icecc_tarball" ]; then		if [ -f "$icecc_tarball" ]; then
	export ICECC_VERSION="i486:$icecc_tarball"		export ICECC_VERSION="i486:$icecc_tarball"

imported_>mairas: added a warning about failing arm compilations

2010-02-09T11:50:07Z

added a warning about failing arm compilations

← Older revision		Revision as of 11:50, 9 February 2010
Line 2:		Line 2:

	= Icecream + Scratchbox HOWTO =		= Icecream + Scratchbox HOWTO =

			'''''NB:''' With some Scratchbox versions, distributed arm target compilations occasionally fail due to gcc/g++ targeting wrong ARM variant. Once a workaround is developed, this warning will disappear.''

	From Icecream web page <ref>http://en.opensuse.org/Icecream</ref>:		From Icecream web page <ref>http://en.opensuse.org/Icecream</ref>:

imported_>mairas: IcecreamScratchboxHowto moved to Icecream Scratchbox Howto: Avoid CamelCase

2010-02-09T11:38:56Z

IcecreamScratchboxHowto moved to Icecream Scratchbox Howto: Avoid CamelCase

← Older revision		Revision as of 11:38, 9 February 2010
(No difference)

imported_>mairas: /* Using icecc */

2010-02-09T11:34:18Z

Using icecc

← Older revision		Revision as of 11:34, 9 February 2010
Line 124:		Line 124:
	export ICECC_VERSION="i486:$icecc_tarball"		export ICECC_VERSION="i486:$icecc_tarball"
	# comment the following line if you don't want to build in parallel by default		# comment the following line if you don't want to build in parallel by default
	MAKEFLAGS="-j12"		export MAKEFLAGS="-j12"
	fi		fi
	unset icecc_tarball sbox_compiler		unset icecc_tarball sbox_compiler

imported_>mairas at 09:23, 9 February 2010

2010-02-09T09:23:27Z

← Older revision		Revision as of 09:23, 9 February 2010
Line 1:		Line 1:
	''Original instructions written by Anderson Lizardo~~. This version copied verbatim from the INdT wiki~~.''		''Original instructions written by Anderson Lizardo.''

	= Icecream + Scratchbox HOWTO =		= Icecream + Scratchbox HOWTO =

192.100.116.142: Added a prerequisites section and some notes in the actual instructions.

2010-02-09T09:21:57Z

Added a prerequisites section and some notes in the actual instructions.

@@ Line 11: / Line 11: @@
 This document describes how to use icrecream for parallel compilation inside
 Scratchbox.
 == Compiling icecc ==
@@ Line 54: / Line 87: @@
 <li>Run the script for each target you wish to use icecc for. E.g.:</li>
 <pre>
-host$ ./icecc_create_env_sbox.sh maemo5-armv7
+host$ ./icecc_create_env_sbox.sh FREMANTLE_ARMEL
-host$ ./icecc_create_env_sbox.sh maemo5-i486
+host$ ./icecc_create_env_sbox.sh FREMANTLE_X86
 </pre>
 </ol>
@@ Line 63: / Line 96: @@
 * a symbolic link to this tarball, named "icecc_box-<compiler_name>.tar.gz"
-These tarballs will be used later when running icecc. It is important that they uniquely identify the toolchain, because all peers in the build network will use the same tarball, and will cache the toolchain locally using that name. Therefore we use the MD5 signature, plus a symlink to easily map it to the actual Scratchbox toolchain name.
+Place the tarballs in $HOME/icecc inside Scratchbox. These tarballs will be used later when running icecc. It is important that they uniquely identify the toolchain, because all peers in the build network will use the same tarball, and will cache the toolchain locally using that name. Therefore we use the MD5 signature, plus a symlink to easily map it to the actual Scratchbox toolchain name.
 == Using icecc ==
@@ Line 89: / Line 122: @@
 icecc_tarball="$(readlink -f $HOME/icecc_sbox-$sbox_compiler.tar.gz)"
 if [ -f "$icecc_tarball" ]; then
-export ICECC_VERSION="i486:$icecc_tarball"
+    export ICECC_VERSION="i486:$icecc_tarball"
 fi
 unset icecc_tarball sbox_compiler
@@ Line 121: / Line 156: @@
 </pre>
 </ol>
 You can now build applications normally and they will automatically use icecc when calling gcc or g++.

imported_>mairas at 08:05, 8 February 2010

2010-02-08T08:05:48Z

← Older revision		Revision as of 08:05, 8 February 2010
Line 1:		Line 1:
			''Original instructions written by Anderson Lizardo. This version copied verbatim from the INdT wiki.''

	= Icecream + Scratchbox HOWTO =		= Icecream + Scratchbox HOWTO =

	~~''Original instructions written by Anderson Lizardo. This version copied verbatim from the INdT wiki.''~~

	From Icecream web page <ref>http://en.opensuse.org/Icecream</ref>:		From Icecream web page <ref>http://en.opensuse.org/Icecream</ref>:

imported_>mairas: New page: = Icecream + Scratchbox HOWTO = ''Original instructions written by Anderson Lizardo. This version copied verbatim from the INdT wiki.'' From Icecream web page http://en.opensuse.org...

2010-02-08T08:05:15Z

New page: = Icecream + Scratchbox HOWTO = ''Original instructions written by Anderson Lizardo. This version copied verbatim from the INdT wiki.'' From Icecream web page <ref>http://en.opensuse.org...

New page

= Icecream + Scratchbox HOWTO =

''Original instructions written by Anderson Lizardo. This version copied verbatim from the INdT wiki.''

From Icecream web page <ref>http://en.opensuse.org/Icecream</ref>:

"Icecream is created by SUSE and is based on ideas and code by distcc. Like
distcc it takes compile jobs from your build and distributes it to remote
machines allowing a parallel build on several machines you've got."

This document describes how to use icrecream for parallel compilation inside
Scratchbox.

== Compiling icecc ==

To be able to use icecc both on ARM and x86 targets, we need to compile it use
the "special" host-gcc and host-g++ compilers inside a scratchbox target. The
binaries generated by these compilers can then be run from any target, because
they link to scratchbox own libraries.

We will use only the icecc client, and share the icecc daemon with the host.
This allows using icecc both inside and outside scratchbox.

To compile icecc, enter a scratchbox target (the architecture set on it is not
important) and unpack the icecc source tarball (you can download it from <ref>ftp://ftp.suse.com/pub/projects/icecream/</ref>).
Next, enter the source directory and run:

<pre>
sbox > ./configure --prefix=/scratchbox/tools CC=host-gcc CXX=host-g++
sbox > make
</pre>

== Installing icecc ==

The next commands should be done outside scratchbox, as root.

Copy the "client/icecc" binary to /scratchbox/tools/bin and a "icecc++"
symlink necessary for compiling C++ programs:

<pre>
host# cp -a client/icecc /scratchbox/tools/bin/icecc
host# ln -sfn icecc /scratchbox/tools/bin/icecc++
</pre>

== Preparing toolchain tarballs ==

To make sure that the correct compiler is used, it is necessary to create a
tarball containing all files required by the toolchain. This can be done either
manually, or by using the "icecc_create_env_sbox.sh" script.

<ol>
<li>Download [[Media:Icecc_create_env_sbox.sh|icecc_create_env_sbox.sh]] script.</li>
<li>(Optional) Edit the script and change the "sbox_dir" variable, in case your scratchbox is not installed in /scratchbox</li>
<li>Run the script for each target you wish to use icecc for. E.g.:</li>
<pre>
host$ ./icecc_create_env_sbox.sh maemo5-armv7
host$ ./icecc_create_env_sbox.sh maemo5-i486
</pre>
</ol>

For each run, two files will be created:
* a tarball named <md5>.tar.gz, where <md5> is the MD5 signature of the tarball contents.
* a symbolic link to this tarball, named "icecc_box-<compiler_name>.tar.gz"

These tarballs will be used later when running icecc. It is important that they uniquely identify the toolchain, because all peers in the build network will use the same tarball, and will cache the toolchain locally using that name. Therefore we use the MD5 signature, plus a symlink to easily map it to the actual Scratchbox toolchain name.

== Using icecc ==

In order to run icecc, you need to set the ICECC_VERSION environment variable
to point to the tarball created in previous section. Note that this variable
will be set to different values, depending on which target icecc will run (ARM
or x86).

The ICECC_VERSION variable has the following format:

<pre>
<build_architecture>:<cross_toolchain_for_target>
</pre>

Hint:

You can add the following snippet to ~/.bashrc (inside scratchbox) and have
that variable set automatically to the right value (change tarball names and
path accordingly):

<pre>
sbox_compiler="$(sb-conf show --compiler)"
# use the tarball name with the MD5, avoiding conflicting names in peer caches
icecc_tarball="$(readlink -f $HOME/icecc_sbox-$sbox_compiler.tar.gz)"
if [ -f "$icecc_tarball" ]; then
export ICECC_VERSION="i486:$icecc_tarball"
fi
unset icecc_tarball sbox_compiler
</pre>

Done! To effectively use icecc to compile code, set the compiler to "icecc".
This is usually done by setting the CC and CXX environment variables.

== Using icecc "transparently" under Scratchbox ==

Modifying build systems to use "icecc" instead of the defaults g++/gcc can be error prone. Therefore, the following instructions can be used to make it transparent:

<ol>
<li>Create a "/host_usr/bin" directory if it does not exist already:</li>

<pre>sbox > mkdir -p /host_usr/bin</pre>

(This directory is automatically added by Scratchbox to beginning of the PATH, therefore it is not necessary to add it manually.)

<li>Create "gcc" and "g++" symlinks into that directory, pointing to icecc:</li>

<pre>
sbox > ln -sfn /scratchbox/tools/bin/icecc /host_usr/bin/gcc
sbox > ln -sfn /scratchbox/tools/bin/icecc++ /host_usr/bin/g++
</pre>

<li>Disable Scratchbox redirection for the gcc and g++ binaries:</li>

<pre>
sbox > export SBOX_REDIRECT_IGNORE=/usr/bin/gcc,/usr/bin/g++
</pre>
</ol>

You can now build applications normally and they will automatically use icecc when calling gcc or g++.

== References ==

<references/>

[[Category:Development]]
[[Category:Scratchbox]]