documentation/sdk-manual/appendix-obtain.rst

1 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
7 Locating Pre-Built SDK Installers
10 You can use existing, pre-built toolchains by locating and running an
12 method, you select and download an architecture-specific SDK installer
13 and then run the script to hand-install the toolchain.
15 Follow these steps to locate and hand-install the toolchain:
17 1. *Go to the Installers Directory:* Go to
18    :yocto_dl:`/releases/yocto/yocto-&DISTRO;/toolchain/`
22    ``i686`` for 32-bit machines or ``x86_64`` for 64-bit machines).
30       poky-glibc-host_system-core-image-type-arch-toolchain[-ext]-release.sh
40                  "aarch64", "armv5e", "core2-64", "cortexa8hf-neon", "i586", "mips32r2",
46              The standard SDK installer does not have the "-ext" string as
51    Project are based off of the ``core-image-sato`` and
52    ``core-image-minimal`` images and contain libraries appropriate for
55    For example, if your build host is a 64-bit x86 system and you need
56    an extended SDK for a 64-bit core2 target, go into the ``x86_64``
59       poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh
63    directory::
65       $ ~/Downloads/poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh
69    ":ref:`sdk-manual/appendix-obtain:installed standard sdk directory structure`"
71    ":ref:`sdk-manual/appendix-obtain:installed extensible sdk directory structure`"
81    in a shell. See the ":ref:`dev-manual/start:preparing the build host`" section
87    Yocto Project :term:`Source Directory`
89    ``poky`` repository). See the ":ref:`dev-manual/start:cloning the \`\`poky\`\` repository`" and
90    possibly the ":ref:`dev-manual/start:checking out by branch in poky`" and
91    ":ref:`dev-manual/start:checking out by tag in poky`" sections
96 3. *Initialize the Build Environment:* While in the root directory of
97    the Source Directory (i.e. ``poky``), run the
98    :ref:`structure-core-script` environment
103       $ source oe-init-build-env
106    creates the :term:`Build Directory`,
108    ``build`` in this case and is located in the Source Directory. After
109    the script runs, your current working directory is set to the
110    ``build`` directory.
115    ``local.conf`` file in your Build Directory matches the architecture
122    in the ``local.conf`` file in your Build Directory is correctly set.
134 …K can currently only be built for the same architecture as the machine being built on - SDK_ARCH is
141    sure to replace ``image`` with an image (e.g. "core-image-sato")::
143       $ bitbake image -c populate_sdk
147       $ bitbake image -c populate_sdk_ext
153    ``tmp/deploy/sdk`` in the Build Directory.
157       -  By default, the previous BitBake command does not build static
167          libc-staticdev"
170    ``tmp/deploy/sdk`` in the Build Directory. Following is an example::
173       $ ./poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh
177    ":ref:`sdk-manual/appendix-obtain:installed standard sdk directory structure`"
179    ":ref:`sdk-manual/appendix-obtain:installed extensible sdk directory structure`"
188 -  You want to boot the image using NFS.
190 -  You want to use the root filesystem as the target sysroot.
192 -  You want to develop your target application using the root filesystem
197 1. *Locate and Download the Tarball for the Pre-Built Root Filesystem
200    in machine-specific folders in the
201    :yocto_dl:`Index of Releases </releases/yocto/yocto-&DISTRO;/machines/>`
202    in the "machines" directory.
204    The machine-specific folders of the "machines" directory contain
209    The pre-built root filesystem image files follow these naming
212       core-image-profile-arch.tar.bz2
216                     lsb, lsb-dev, lsb-sdk, minimal, minimal-dev, minimal-initramfs,
217                     sato, sato-dev, sato-sdk, sato-sdk-ptest. For information on
222                     beaglebone-yocto, beaglebone-yocto-lsb, edgerouter, edgerouter-lsb,
223                     genericx86, genericx86-64, genericx86-64-lsb, genericx86-lsb and qemu*.
226    provided by the Yocto Project are based off of the
227    ``core-image-sato`` and ``core-image-minimal`` images.
230    hardware and your image is a ``core-image-sato-sdk`` image, you can
233       core-image-sato-sdk-beaglebone-yocto.tar.bz2
235 2. *Initialize the Cross-Development Environment:* You must ``source``
236    the cross-development environment setup script to establish necessary
239    This script is located in the top-level directory in which you
242    Following is an example based on the toolchain installed in the
243    ":ref:`sdk-manual/appendix-obtain:locating pre-built sdk installers`" section::
245       $ source poky_sdk/environment-setup-core2-64-poky-linux
247 3. *Extract the Root Filesystem:* Use the ``runqemu-extract-sdk``
252    from the :yocto_dl:`Index of Releases </releases/yocto/yocto-&DISTRO;/machines/>`.
253    This command extracts the root filesystem into the ``core2-64-sato``
254    directory::
256 …   $ runqemu-extract-sdk ~/Downloads/core-image-sato-sdk-beaglebone-yocto.tar.bz2 ~/beaglebone-sato
258    You could now point to the target sysroot at ``beaglebone-sato``.
260 Installed Standard SDK Directory Structure
263 The following figure shows the resulting directory structure after you
267 .. image:: figures/sdk-installed-standard-sdk-directory.png
277 portions of the file or directory name. For example, install_dir/version
278 is the directory where the SDK is installed. By default, this directory
283 directories within the ``sysroots`` could be ``i586-poky-linux`` and
284 ``x86_64-pokysdk-linux`` for the target and host, respectively.
286 Installed Extensible SDK Directory Structure
289 The following figure shows the resulting directory structure after you
293 .. image:: figures/sdk-installed-extensible-sdk-directory.png
297 The installed directory structure for the extensible SDK is quite
303 Of note in the directory structure are an environment setup script for
309 portions of the file or directory name. For example, install_dir is the
310 directory where the SDK is installed, which is ``poky_sdk`` by default,