Recall that earlier we talked about how to use an existing toolchain tarball that had been installed into /opt/poky, which is outside of the Poky build environment (see “Using an Existing Toolchain Tarball”). And, that sourcing your architecture-specific environment setup script initializes a suitable development environment. This setup occurs by adding the compiler, QEMU scripts, QEMU binary, a special version of pkgconfig and other useful utilities to the PATH variable. Variables to assist pkgconfig and autotools are also defined so that, for example, configure.sh can find pre-generated test results for tests that need target hardware on which to run. These conditions allow you to easily use the toolchain outside of the Poky build environment on both autotools-based projects and makefile-based projects.

For an autotools-based project you can use the cross-toolchain by just passing the appropriate host option to configure.sh. The host option you use is derived from the name of the environment setup script in /opt/poky resulting from unpacking the cross-toolchain tarball. For example, the host option for an ARM-based target that uses the GNU EABI is armv5te-poky-linux-gnueabi. Note that the name of the script is environment-setup-armv5te-poky-linux-gnueabi. Thus, the following command works: $ configure ‐‐host-armv5te-poky-linux-gnueabi ‐‐with-libtool-sysroot=<sysroot-dir> This single command updates your project and rebuilds it using the appropriate cross-toolchain tools.

For a makefile-based project you use the cross-toolchain by making sure the tools are used. You can do this as follows: CC=arm-poky-linux-gnueabi-gcc LD=arm-poky-linux-gnueabi-ld CFLAGS=”${CFLAGS} ‐‐sysroot=<sysroot-dir>” CXXFLAGS=”${CXXFLAGS} ‐‐sysroot=<sysroot-dir>”