You can use existing, pre-built toolchains by locating and running an SDK installer script that ships with the Yocto Project. Using this method, you select and download an architecture-specific SDK installer and then run the script to hand-install the toolchain.
Follow these steps to locate and hand-install the toolchain:
Go to the Installers Directory: Go to http://downloads.yoctoproject.org/releases/yocto/yocto-2.7/toolchain/
Open the Folder for Your Build Host:
Open the folder that matches your
build host
(i.e. i686
for 32-bit machines or
x86_64
for 64-bit machines).
Locate and Download the SDK Installer: You need to find and download the installer appropriate for your build host, target hardware, and image type.
The installer files (*.sh
) follow
this naming convention:
poky-glibc-host_system
-core-image-type
-arch
-toolchain[-ext]-release
.sh Where:host_system
is a string representing your development system: "i686" or "x86_64"type
is a string representing the image: "sato" or "minimal"arch
is a string representing the target architecture: "aarch64", "armv5e", "core2-64", "coretexa8hf-neon", "i586", "mips32r2", "mips64", or "ppc7400"release
is the version of Yocto Project. NOTE: The standard SDK installer does not have the "-ext" string as part of the filename.
The toolchains provided by the Yocto Project are based off of
the core-image-sato
and
core-image-minimal
images and contain
libraries appropriate for developing against those images.
For example, if your build host is a 64-bit x86 system
and you need an extended SDK for a 64-bit core2 target, go
into the x86_64
folder and download the
following installer:
poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-2.7.sh
Run the Installer:
Be sure you have execution privileges and run the installer.
Following is an example from the Downloads
directory:
$ ~/Downloads/poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-2.7.sh
During execution of the script, you choose the root location for the toolchain. See the "Installed Standard SDK Directory Structure" section and the "Installed Extensible SDK Directory Structure" section for more information.