From 7233e359ddc50c80415c746449c33aa0fe83862d Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 21 Mar 2016 14:25:47 -0700 Subject: sdk-manual: Edits to add extensible SDK configuration sections. (From yocto-docs rev: 378bbceb8ea06c225c4758807e25a35521faa3a9) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/sdk-manual/sdk-appendix-obtain.xml | 82 +++++------------------- 1 file changed, 16 insertions(+), 66 deletions(-) (limited to 'documentation/sdk-manual/sdk-appendix-obtain.xml') diff --git a/documentation/sdk-manual/sdk-appendix-obtain.xml b/documentation/sdk-manual/sdk-appendix-obtain.xml index 6ffc958695..daa5e79fe8 100644 --- a/documentation/sdk-manual/sdk-appendix-obtain.xml +++ b/documentation/sdk-manual/sdk-appendix-obtain.xml @@ -52,18 +52,20 @@ As an alternative to locating and downloading a toolchain installer, - you can build the toolchain installer if you have a - Build Directory. - - Although not the preferred method, it is also possible to use - bitbake meta-toolchain to build the toolchain - installer. - If you do use this method, you must separately install and extract - the target sysroot. - For information on how to install the sysroot, see the - "Extracting the Root Filesystem" - section. - + you can build the toolchain 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). @@ -80,54 +82,6 @@ that matches your target root filesystem. - - Another powerful feature is that the toolchain is completely - self-contained. - The binaries are linked against their own copy of - libc, which results in no dependencies - on the target system. - To achieve this, the pointer to the dynamic loader is - configured at install time since that path cannot be dynamically - altered. - This is the reason for a wrapper around the - populate_sdk and - populate_sdk_ext archives. - - - - Another feature is that only one set of cross-canadian toolchain - binaries are produced per architecture. - This feature takes advantage of the fact that the target hardware can - be passed to gcc as a set of compiler options. - Those options are set up by the environment script and contained in - variables such as - CC - and - LD. - This reduces the space needed for the tools. - Understand, however, that a sysroot is still needed for every target - since those binaries are target-specific. - - - - Remember, before using any BitBake command, you - must source the build environment setup script - (i.e. - &OE_INIT_FILE; - 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 @@ -154,12 +108,8 @@ Extracting the Root Filesystem - After installing the toolchain or building it using BitBake, - you need a root filesystem, which you need to separately extract. - - - - Here are some cases where you need to extract the root filesystem: + After installing the toolchain, for some use cases you + might need to separately extract a root filesystem: You want to boot the image using NFS. -- cgit v1.2.3-54-g00ecf