As an alternative to locating and downloading a SDK installer,
you can build the SDK installer assuming you have first sourced
the environment setup script.
See the
"Building Images"
section in the Yocto Project Quick Start for steps that show you
how to set up the Yocto Project environment.
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).
To build the SDK installer for a standard SDK and populate the SDK image, use the following command:
$ bitbake image
-c populate_sdk
You can do the same for the extensible SDK using this command:
$ bitbake image
-c populate_sdk_ext
These commands result in a SDK installer that contains the sysroot that matches your target root filesystem.
When the bitbake
command completes, the SDK
installer will be in
tmp/deploy/sdk
in the Build Directory.
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 glibc
static development libraries:
IMAGE_INSTALL_append = " glibc-staticdev"
For additional information on building the installer, see the Cookbook guide to Making an Eclipse Debug Capable Image wiki page.