diff options
Diffstat (limited to 'documentation/sdk-manual/sdk-appendix-obtain.xml')
| -rw-r--r-- | documentation/sdk-manual/sdk-appendix-obtain.xml | 82 |
1 files changed, 16 insertions, 66 deletions
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 @@ <para> As an alternative to locating and downloading a toolchain installer, - you can build the toolchain installer if you have a - <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>. - <note> - Although not the preferred method, it is also possible to use - <filename>bitbake meta-toolchain</filename> 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 - "<link linkend='sdk-extracting-the-root-filesystem'>Extracting the Root Filesystem</link>" - section. - </note> + you can build the toolchain installer assuming you have first sourced + the environment setup script. + See the + "<ulink url='&YOCTO_DOCS_QS_URL;#qs-building-images'>Building Images</ulink>" + 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 + <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink> + variable matches the architecture for which you are building and that + the + <ulink url='&YOCTO_DOCS_REF_URL;#var-SDKMACHINE'><filename>SDKMACHINE</filename></ulink> + 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). </para> <para> @@ -81,54 +83,6 @@ </para> <para> - Another powerful feature is that the toolchain is completely - self-contained. - The binaries are linked against their own copy of - <filename>libc</filename>, 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 - <filename>populate_sdk</filename> and - <filename>populate_sdk_ext</filename> archives. - </para> - - <para> - 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 <filename>gcc</filename> as a set of compiler options. - Those options are set up by the environment script and contained in - variables such as - <ulink url='&YOCTO_DOCS_REF_URL;#var-CC'><filename>CC</filename></ulink> - and - <ulink url='&YOCTO_DOCS_REF_URL;#var-LD'><filename>LD</filename></ulink>. - 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. - </para> - - <para> - Remember, before using any BitBake command, you - must source the build environment setup script - (i.e. - <ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink> - or - <ulink url='&YOCTO_DOCS_REF_URL;#structure-memres-core-script'><filename>oe-init-build-env-memres</filename></ulink>) - located in the Source Directory and you must make sure your - <filename>conf/local.conf</filename> variables are correct. - In particular, you need to be sure the - <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink> - variable matches the architecture for which you are building and that - the - <ulink url='&YOCTO_DOCS_REF_URL;#var-SDKMACHINE'><filename>SDKMACHINE</filename></ulink> - 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). - </para> - - <para> When the <filename>bitbake</filename> command completes, the toolchain installer will be in <filename>tmp/deploy/sdk</filename> in the Build Directory. @@ -154,12 +108,8 @@ <title>Extracting the Root Filesystem</title> <para> - After installing the toolchain or building it using BitBake, - you need a root filesystem, which you need to separately extract. - </para> - - <para> - 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: <itemizedlist> <listitem><para>You want to boot the image using NFS. </para></listitem> |