sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

documentation/adt-manual/adt-prepare.xml: Re-worded toolchain generation 

The section that describes how to generate the cross-toolchain into the
Yocto build tree erroneously referred to this process as installing the
toolchain.  Furthermore, it actually mentioned the creation of a
toolchain tarball, which is wrong.  I updated the section to more properly
refer to this procedure as generating the toolchain.  I also removed the
bit about the tarball creation.

(From yocto-docs rev: 5ae8faa651ed6bf22c5475a4eacb5c758c62cea1)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2012-06-22 09:36:48 -07:00 committed by Richard Purdie
parent 73411842a6
commit 9234b282aa
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
documentation/adt-manual/adt-prepare.xml
View File

@ -255,15 +255,16 @@
<title>Using BitBake and the Yocto Project Build Tree</title> <title>Using BitBake and the Yocto Project Build Tree</title>
<para> <para>
A final way of installing just the cross-toolchain is to use BitBake to build the A final way of making the cross-toolchain available is to use BitBake
toolchain within an existing Yocto Project build tree. to generate the toolchain within an existing Yocto Project build tree.
This method does not install the toolchain into the <filename>/opt</filename> directory. This method does not install the toolchain into the
<filename>/opt</filename> directory.
As with the previous method, if you need to install the target sysroot, you must As with the previous method, if you need to install the target sysroot, you must
do this separately. do this separately.
</para> </para>
<para> <para>
Follow these steps to build and install the toolchain into the build tree: Follow these steps to generate the toolchain into the build tree:
<orderedlist> <orderedlist>
<listitem><para>Source the environment setup script <listitem><para>Source the environment setup script
<filename>oe-init-build-env</filename> located in the Yocto Project <filename>oe-init-build-env</filename> located in the Yocto Project
@ -281,7 +282,7 @@
<filename>local.conf</filename> file and re-run the BitBake <filename>local.conf</filename> file and re-run the BitBake
command.</note></para></listitem> command.</note></para></listitem>
<listitem><para>Run <filename>bitbake meta-ide-support</filename> to complete the <listitem><para>Run <filename>bitbake meta-ide-support</filename> to complete the
cross-toolchain installation. cross-toolchain generation.
<note>If you change out of your working directory after you <note>If you change out of your working directory after you
<filename>source</filename> the environment setup script and before you run <filename>source</filename> the environment setup script and before you run
the <filename>bitbake</filename> command, the command might not work. the <filename>bitbake</filename> command, the command might not work.
@ -289,7 +290,7 @@
after checking or editing the <filename>local.conf</filename> but without after checking or editing the <filename>local.conf</filename> but without
changing out of your working directory.</note> changing out of your working directory.</note>
Once the <filename>bitbake</filename> command finishes, Once the <filename>bitbake</filename> command finishes,
the tarball for the cross-toolchain is generated within the Yocto Project build tree. the cross-toolchain is generated and populated within the Yocto Project build tree.
You will notice environment setup files for the cross-toolchain in the You will notice environment setup files for the cross-toolchain in the
Yocto Project build tree in the <filename>tmp</filename> directory. Yocto Project build tree in the <filename>tmp</filename> directory.
Setup script filenames contain the strings <filename>environment-setup</filename>. Setup script filenames contain the strings <filename>environment-setup</filename>.