Openembedded.org - User contributions [en]

SDK/Toolchain/Application Developer Toolkit

2010-12-23T19:55:13Z

Bgamari:

Along with recipes for building a compiler for internal its own use, OpenEmbedded has recipes to create a full cross-compiler environment for the host. First, you need to have a working OpenEmbedded environment (see [[Getting_started]]). Note that throughout this article we will use the example of working on the ARM architecture. While particular file names may differ in your case, the general process should be similar. To build the cross-compiler, build the <tt>meta-toolchain</tt> recipe,

<pre><nowiki>
$ bitbake meta-toolchain
</nowiki></pre>

This will produce a tarball in a subdirectory of <tt>deploy/sdk</tt>. This tarball includes compiler executables, libraries, and core headers, as well as a small environment script, all under the prefix of <tt>usr/local/angstrom</tt>. To install this tarball, simply untar into <tt>/</tt>,

<pre><nowiki>
$ sudo tar -C / -pxvjf $SDK_ROOT/sdk-
</nowiki></pre>

To cross-compile a package for your target platform, simply source the provided <tt>environment-setup</tt> script and compile as usual,
<pre><nowiki>
$ source /usr/local/angstrom/arm/environment-setup
$ make
</nowiki></pre>
Note that the meta-toolchain environment does not include any of the libraries included in your target image.

= Installing libraries and headers =
Along with a compiler, the meta-toolchain also comes with an installation of <tt>opkg</tt> with which one can install libraries into your cross-compilation environment. To install packages for use in cross-compiling use the <tt>opkg-target</tt> executable (not <tt>opkg</tt>; does anyone know what the latter is for?) There are a few For instance, to install the development headers for the boost library (<tt>boost-dev</tt>),

<pre><nowiki>
$ sudo -i
# source /usr/local/angstrom/arm/environment-setup
# opkg-target update
# opkg-target install boost-dev
</nowiki></pre>

This will fetch a package list from the Angstrom repository then fetch and install the boost package.

= Cross-compiling the kernel =
Because of the self-contained nature of the kernel, one must proceed slightly differently than with cross-compiling user-mode software. Namely, one must not use the <tt>environment-setup</tt> script provided with <tt>meta-toolchain</tt>. This script modifies environment required by the host compiler used to compile tools used during the build process, resulting in difficult to trace errors.[http://thread.gmane.org/gmane.linux.kbuild.devel/5686/focus=39837][http://thread.gmane.org/gmane.linux.kernel/1015620/focus=5621]

Instead, one simply must pass the target architecture and the cross-compiler executable name prefix to Kbuild,

<pre><nowiki>
$ cd linux-2.6
$ export ARCH=arm
$ export CROSS_COMPILE=/usr/local/angstrom/arm/bin/
$ make menuconfig
$ make
</nowiki></pre>

The kernel Makefile also contains useful rules for packing the kernel image and modules into a tarball, for easy installation on the target,

<pre><nowiki>
$ make
</nowiki></pre>

= Other Resources =
The OpenMoko wiki has a very useful page[http://wiki.openmoko.org/wiki/Toolchain] describing toolchain installation and usage.

SDK/Toolchain/Application Developer Toolkit

2010-12-23T19:52:51Z

Bgamari:

Along with recipes for building a compiler for internal its own use, OpenEmbedded has recipes to create a full cross-compiler environment for the host. First, you need to have a working OpenEmbedded environment (see [[Getting_started]]). Note that throughout this article we will use the example of working on the ARM architecture. While particular file names may differ in your case, the general process should be similar. To build the cross-compiler, build the <tt>meta-toolchain</tt> recipe,

<pre><nowiki>
$ bitbake meta-toolchain
</nowiki></pre>

This will produce a tarball in a subdirectory of <tt>deploy/sdk</tt>. This tarball includes compiler executables, libraries, and core headers, as well as a small environment script, all under the prefix of <tt>usr/local/angstrom</tt>. To install this tarball, simply untar into <tt>/</tt>,

<pre><nowiki>
$ sudo tar -C / -pxvjf $SDK_ROOT/sdk-
</nowiki></pre>

To cross-compile a package for your target platform, simply source the provided <tt>environment-setup</tt> script and compile as usual,
<pre><nowiki>
$ source /usr/local/angstrom/arm/environment-setup
$ make
</nowiki></pre>
Note that the meta-toolchain environment does not include any of the libraries included in your target image.

= Installing libraries =
Along with a compiler, the meta-toolchain also comes with an installation of <tt>opkg</tt> with which one can install libraries into your cross-compilation environment. To install packages for use in cross-compiling use the <tt>opkg-target</tt> executable (not <tt>opkg</tt>; does anyone know what the latter is for?) There are a few For instance, to install the boost library,

<pre><nowiki>
$ sudo -i
# source /usr/local/angstrom/arm/environment-setup
# opkg-target update
# opkg-target install boost
</nowiki></pre>

This will fetch a package list from the Angstrom repository then fetch and install the boost package.

= Cross-compiling the kernel =
Because of the self-contained nature of the kernel, one must proceed slightly differently than with cross-compiling user-mode software. Namely, one must not use the <tt>environment-setup</tt> script provided with <tt>meta-toolchain</tt>. This script modifies environment required by the host compiler used to compile tools used during the build process, resulting in difficult to trace errors.[http://thread.gmane.org/gmane.linux.kbuild.devel/5686/focus=39837][http://thread.gmane.org/gmane.linux.kernel/1015620/focus=5621]

Instead, one simply must pass the target architecture and the cross-compiler executable name prefix to Kbuild,

<pre><nowiki>
$ cd linux-2.6
$ export ARCH=arm
$ export CROSS_COMPILE=/usr/local/angstrom/arm/bin/
$ make menuconfig
$ make
</nowiki></pre>

The kernel Makefile also contains useful rules for packing the kernel image and modules into a tarball, for easy installation on the target,

<pre><nowiki>
$ make
</nowiki></pre>

= Other Resources =
The OpenMoko wiki has a very useful page[http://wiki.openmoko.org/wiki/Toolchain] describing toolchain installation and usage.

SDK/Toolchain/Application Developer Toolkit

2010-12-23T19:51:38Z

Bgamari:

Along with recipes for building a compiler for internal its own use, OpenEmbedded has recipes to create a full cross-compiler environment for the host. First, you need to have a working OpenEmbedded environment (see [[Getting_started]]). Note that throughout this article we will use the example of working on the ARM architecture. While particular file names may differ in your case, the general process should be similar. To build the cross-compiler, build the <tt>meta-toolchain</tt> recipe,

<pre><nowiki>
$ bitbake meta-toolchain
</nowiki></pre>

This will produce a tarball in a subdirectory of <tt>deploy/sdk</tt>. This tarball includes compiler executables, libraries, and core headers, as well as a small environment script, all under the prefix of <tt>usr/local/angstrom</tt>. To install this tarball, simply untar into <tt>/</tt>,

<pre><nowiki>
$ sudo tar -C / -pxvjf $SDK_ROOT/sdk-
</nowiki></pre>

To cross-compile a package for your target platform, simply source the provided <tt>environment-setup</tt> script and compile as usual,
<pre><nowiki>
$ source /usr/local/angstrom/arm/environment-setup
$ make
</nowiki></pre>
Note that the meta-toolchain environment does not include any of the libraries included in your target image.

= Installing libraries =
Along with a compiler, the meta-toolchain also comes with an installation of <tt>opkg</tt> with which one can install libraries into your cross-compilation environment. To install packages for use in cross-compiling use the <tt>opkg-target</tt> executable (not <tt>opkg</tt>; does anyone know what the latter is for?) There are a few For instance, to install the boost library,

<pre><nowiki>
$ sudo -i
# source /usr/local/angstrom/arm/environment-setup
# opkg-target update
# opkg-target install boost
</nowiki></pre>

= Cross-compiling the kernel =
Because of the self-contained nature of the kernel, one must proceed slightly differently than with cross-compiling user-mode software. Namely, one must not use the <tt>environment-setup</tt> script provided with <tt>meta-toolchain</tt>. This script modifies environment required by the host compiler used to compile tools used during the build process, resulting in difficult to trace errors.[http://thread.gmane.org/gmane.linux.kbuild.devel/5686/focus=39837][http://thread.gmane.org/gmane.linux.kernel/1015620/focus=5621]

Instead, one simply must pass the target architecture and the cross-compiler executable name prefix to Kbuild,

<pre><nowiki>
$ cd linux-2.6
$ export ARCH=arm
$ export CROSS_COMPILE=/usr/local/angstrom/arm/bin/
$ make menuconfig
$ make
</nowiki></pre>

The kernel Makefile also contains useful rules for packing the kernel image and modules into a tarball, for easy installation on the target,

<pre><nowiki>
$ make
</nowiki></pre>

= Other Resources =
The OpenMoko wiki has a very useful page[http://wiki.openmoko.org/wiki/Toolchain] describing toolchain installation and usage.

SDK/Toolchain/Application Developer Toolkit

2010-12-22T18:14:33Z

Bgamari:

Along with recipes for building a compiler for internal its own use, OpenEmbedded has recipes to create a full cross-compiler environment for the host. First, you need to have a working OpenEmbedded environment (see [[Getting_started]]). Note that throughout this article we will use the example of working on the ARM architecture. While particular file names may differ in your case, the general process should be similar. To build the cross-compiler, build the <tt>meta-toolchain</tt> recipe,

<pre><nowiki>
$ bitbake meta-toolchain
</nowiki></pre>

This will produce a tarball in a subdirectory of <tt>deploy/sdk</tt>. This tarball includes compiler executables, libraries, and core headers, as well as a small environment script, all under the prefix of <tt>usr/local/angstrom</tt>. To install this tarball, simply untar into <tt>/</tt>,

<pre><nowiki>
$ tar -C / -pxvjf $SDK_ROOT/sdk-
</nowiki></pre>

To cross-compile a package for your target platform, simply source the provided <tt>environment-setup</tt> script and compile as usual,
<pre><nowiki>
$ source /usr/local/angstrom/arm/environment-setup
$ make
</nowiki></pre>
Note that the meta-toolchain environment does not include any of the libraries included in your target image.

= Cross-compiling the kernel =
Because of the self-contained nature of the kernel, one must proceed slightly differently than with cross-compiling user-mode software. Namely, one must not use the <tt>environment-setup</tt> script provided with <tt>meta-toolchain</tt>. This script modifies environment required by the host compiler used to compile tools used during the build process, resulting in difficult to trace errors.[http://thread.gmane.org/gmane.linux.kbuild.devel/5686/focus=39837][http://thread.gmane.org/gmane.linux.kernel/1015620/focus=5621]

Instead, one simply must pass the target architecture and the cross-compiler executable name prefix to Kbuild,

<pre><nowiki>
$ cd linux-2.6
$ export ARCH=arm
$ export CROSS_COMPILE=/usr/local/angstrom/arm/bin/
$ make menuconfig
$ make
</nowiki></pre>

The kernel Makefile also contains useful rules for packing the kernel image and modules into a tarball, for easy installation on the target,

<pre><nowiki>
$ make
</nowiki></pre>

SDK/Toolchain/Application Developer Toolkit

2010-12-22T18:14:02Z

Bgamari:

Along with recipes for building a compiler for internal its own use, OpenEmbedded has recipes to create a full cross-compiler environment for the host. First, you need to have a working OpenEmbedded environment (see [[Getting_started]]). Note that throughout this article we will use the example of working on the ARM architecture. While particular file names may differ in your case, the general process should be similar. To build the cross-compiler, build the <tt>meta-toolchain</tt> recipe,

<pre><nowiki>
$ bitbake meta-toolchain
</nowiki></pre>

This will produce a tarball in a subdirectory of <tt>deploy/sdk</tt>. This tarball includes compiler executables, libraries, and core headers, as well as a small environment script, all under the prefix of <tt>usr/local/angstrom</tt>. To install this tarball, simply untar into <tt>/</tt>,

<pre><nowiki>
$ tar -C / -pxvjf $SDK_ROOT/sdk-
</nowiki></pre>

To cross-compile a package for your target platform, simply source the provided <tt>environment-setup</tt> script and compile as usual,
<pre><nowiki>
$ source /usr/local/angstrom/arm/environment-setup
$ make
</nowiki></pre>
Note that the meta-toolchain environment does not include any of the libraries included in your target image.

= Cross-compiling the kernel =
Because of the self-contained nature of the kernel, one must proceed slightly differently than with cross-compiling user-mode software. Namely, one must not use the <tt>environment-setup</tt> script provided with <tt>meta-toolchain</tt>.[http://thread.gmane.org/gmane.linux.kbuild.devel/5686/focus=39837][http://thread.gmane.org/gmane.linux.kernel/1015620/focus=5621] This script modifies environment required by the host compiler used to compile tools used during the build process, resulting in difficult to trace errors.

Instead, one simply must pass the target architecture and the cross-compiler executable name prefix to Kbuild,

<pre><nowiki>
$ cd linux-2.6
$ export ARCH=arm
$ export CROSS_COMPILE=/usr/local/angstrom/arm/bin/
$ make menuconfig
$ make
</nowiki></pre>

The kernel Makefile also contains useful rules for packing the kernel image and modules into a tarball, for easy installation on the target,

<pre><nowiki>
$ make
</nowiki></pre>

SDK/Toolchain/Application Developer Toolkit

2010-12-22T18:12:38Z

Bgamari:

Along with recipes for building a compiler for internal its own use, OpenEmbedded has recipes to create a full cross-compiler environment for the host. First, you need to have a working OpenEmbedded environment (see [[Getting_started]]). Note that throughout this article we will use the example of working on the ARM architecture. While particular file names may differ in your case, the general process should be similar. To build the cross-compiler, build the <tt>meta-toolchain</tt> recipe,

<pre><nowiki>
$ bitbake meta-toolchain
</nowiki></pre>

This will produce a tarball in a subdirectory of <tt>deploy/sdk</tt>. This tarball includes compiler executables, libraries, and core headers, as well as a small environment script, all under the prefix of <tt>usr/local/angstrom</tt>. To install this tarball, simply untar into <tt>/</tt>,

<pre><nowiki>
$ tar -C / -pxvjf $SDK_ROOT/sdk-
</nowiki></pre>

To cross-compile a package for your target platform, simply source the provided <tt>environment-setup</tt> script and compile as usual,
<pre><nowiki>
$ source /usr/local/angstrom/arm/environment-setup
$ make
</nowiki></pre>
Note that the meta-toolchain environment does not include any of the libraries included in your target image.

= Cross-compiling the kernel =
Because of the self-contained nature of the kernel, one must proceed slightly differently than with cross-compiling user-mode software. Namely, one must not use the <tt>environment-setup</tt> script provided with <tt>meta-toolchain</tt>.{{cite web|url=http://thread.gmane.org/gmane.linux.kbuild.devel/5686/focus=39837}}{{cite web|url=http://thread.gmane.org/gmane.linux.kernel/1015620/focus=5621}} This script modifies environment required by the host compiler used to compile tools used during the build process, resulting in difficult to trace errors.

Instead, one simply must pass the target architecture and the cross-compiler executable name prefix to Kbuild,

<pre><nowiki>
$ cd linux-2.6
$ export ARCH=arm
$ export CROSS_COMPILE=/usr/local/angstrom/arm/bin/
$ make menuconfig
$ make
</nowiki></pre>

The kernel Makefile also contains useful rules for packing the kernel image and modules into a tarball, for easy installation on the target,

<pre><nowiki>
$ make
</nowiki></pre>

SDK/Toolchain/Application Developer Toolkit

2010-12-22T18:08:35Z

Bgamari:

SDK/Toolchain/Application Developer Toolkit

2010-12-22T18:05:20Z

Bgamari: /* Cross-compiling the kernel */

SDK/Toolchain/Application Developer Toolkit

2010-12-22T18:04:33Z

Bgamari: Start article