Supported Host Systems
ELDK v5.0 can be installed and run on any recent Linux distribution running on x86 (i686) and x86_64 systems.
Note: 64-bit hosts require a compatibility layer; please see the for details.
Supported Target Architectures
At the moment the following target architectures are supported:
| powerpc | Generic PowerPC target with FPU support Similar to the "ppc_6xx" target in older versions of the ELDK |
| powerpc-softfloat | Generic PowerPC target for FPU-less systems like MPC8308 etc. Similar to the "ppc_8xx" target in older versions of the ELDK |
| armv5te | Generic ARM target for the ARMv5TE architecture (ARM9E, ARM10E, XScale processors) Similar to the "arm" target in older versions of the ELDK |
| armv7a | Generic ARM target for the ARMv7-A architecture (Cortex-A5, -A8, -A9, -A15 processors) Similar to the "armVFP" target in older versions of the ELDK |
Supported Target Configurations
ELDK v5.0 supports a number of different target configurations. These include different sets of target tools and target libraries depending on the primary usage mode of the target system. At this point of time the following configurations are available:
- GMAE/Sato: This configuration is based on the GNOME Mobile & Embedded Initiative (GMAE) software stack. It focuses on mobile devices and provides user interfaces like Pimlico, Clutter, Sato and other GNOME Mobile technologies.
In ELDK v5.0 this is represented by the "eldk-eglibc-*-toolchain-gmae-5.0.tar.bz2" cross tool chain and the "poky-image-sato-sdk-*.tar.gz" target root file system packages.
Select image type "gmae" in the installer to get this configuration. (This is currently the default). - QT Embedded: This configuration uses the Qt application framework.
In ELDK v5.0 this is represented by the "eldk-eglibc-*-toolchain-qte-5.0.tar.bz2" cross tool chain and the "poky-image-qte-sdk-*.tar.gz" target root file system packages.
Select image type "qte" in the installer to get this configuration.
Download Binaries Ready-to-use binaries of ELDK v5.0 are available on our FTP server in the directory.
On the FTP server you can find:
- An install script:
- For each target architecture one directory:
- In each target directory there is:
- a file "*.sha256" with the SHA256 checksums of all provided files
- a configuration file "target.conf" for the install script
- one or more cross tool chain images "eldk-eglibc-*-toolchain-*-5.0.tar.bz2"
- one or more root file system images "poky-image-*-sdk-*.tar.gz"
To install ELDK v5.0 for a specific target architecture please download the install script, the "target.conf" file and the images you want to install.
For example, for a complete installation of the GMAE/Sato configuration of the tool chain and root file system for armv7a targets you would download the following files: $ mkdir eldk-download $ cd eldk-download $ mkdir -p targets/armv7a $ wget ftp://ftp.denx.de/pub/eldk/5.0/install.sh $ cd targets/armv7a $ wget ftp://ftp.denx.de/pub/eldk/5.0/targets/armv7a/target.conf $ wget ftp://ftp.denx.de/pub/eldk/5.0/targets/armv7a/eldk-eglibc-i686-arm-toolchain-gmae-5.0.tar.bz2 $ wget ftp://ftp.denx.de/pub/eldk/5.0/targets/armv7a/poky-image-sato-sdk-armv7a.tar.gz
Make sure to keep the same directory structure on your system, as this is what the install script expects.
Note that it is also an excellent idea to download the file with the SHA256 checksums so you can verify the integrity of your downloads using the "sha256sum -c" command: $ cd eldk-download/targets/armv7a $ wget ftp://ftp.denx.de/pub/eldk/5.0/targets/armv7a/armv7a.sha256 $ sha256sum -c armv7a.sha256 eldk-eglibc-i686-arm-toolchain-gmae-5.0.tar.bz2: OK eldk-eglibc-i686-arm-toolchain-qte-5.0.tar.bz2: OK poky-image-qte-sdk-armv7a.tar.gz: OK poky-image-sato-sdk-armv7a.tar.gz: OK target.conf: OK
Source Code The source code and all needed tools to build ELDK yourself from scratch are available from our repository, see section .
Installation In principle you can install ELDK v5.0 by just unpacking the provided tarballs. There are however a few distinctive requirements that have to be kept in mind:
- The ELDK v5.0 cross tool chain packages are not relocatable and can only be installed into their default location, i. e. into the "/opt/eldk-5.0/" directory.
Note: To be able to do this, you need write permissions in the "/opt/eldk-5.0/" directory. If needed, run for example the command "sudo chmod 01777 /opt/eldk-5.0/". - The root file system images can be installed anywhere, but superuser (root) permissions are needed to install them as they contain device files etc., and exact ownership and permissions of all files must be preserved.
- At the moment, only one target configuration can be installed on a host. This is again a consequence of the fact that the tools are not relocatable. It is possible to install into another directory but then you will have to make software 'think' that it is installed into the default location, for example by using symbolic links or bind mounts (globally visible for all users) or name spaces (may be used on a per-process base), etc. We intentionally leave this to the experienced user here
For the average user we recommend to use the install script which tries to hide these complexities and to provide a simple user interface: install.sh [-d
Origin
Unlike previous versions, starting with the release 5.0 our Embedded Linux Development Kit (ELDK) is based on the .
The Yocto Project is an open-source collaboration project which is driven by the . It targets x86, ARM, MIPS, and Power Architecture based systems. The is used for development and building, which in turn is derived from and intimately connected with the project.
If neither '-s' nor '-r' are given, the default is to install both.
target:
selects the target architecture and defaults to "powerpc"
sdk_arch:
selects the host architecture and defaults to "i686" (at the moment only the 32 bit version of the packages is provided on the FTP server)
Examples