2.4. Optionally Building a Toolchain Installer

As an alternative to locating and downloading a toolchain installer, you can build the toolchain installer one of two ways if you have a Build Directory:

Remember, before using any BitBake command, you must source the build environment setup script (i.e. oe-init-build-env or oe-init-build-env-memres) located in the Source Directory and you must make sure your conf/local.conf variables are correct. In particular, you need to be sure the MACHINE variable matches the architecture for which you are building and that the SDKMACHINE variable is correctly set if you are building a toolchain designed to run on an architecture that differs from your current development host machine (i.e. the build machine).

When the BitBake command completes, the toolchain installer will be in tmp/deploy/sdk in the Build Directory.

Note

By default, this toolchain does not build static binaries. If you want to use the toolchain to build these types of libraries, you need to be sure your image has the appropriate static development libraries. Use the IMAGE_INSTALL variable inside your local.conf file to install the appropriate library packages. Following is an example using eglibc static development libraries:
     IMAGE_INSTALL_append = " eglibc-staticdev"