summaryrefslogtreecommitdiffstats
path: root/documentation/adt-manual
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-06-22 09:36:48 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-06-25 14:57:17 +0100
commit9234b282aaef38c926348d3a08829b0f56c2e538 (patch)
treea15c901550abb724bb4ee1893b73f7e24c6cd99a /documentation/adt-manual
parent73411842a6c71a50790ad7895484fcac3b97ef1d (diff)
downloadast2050-yocto-poky-9234b282aaef38c926348d3a08829b0f56c2e538.zip
ast2050-yocto-poky-9234b282aaef38c926348d3a08829b0f56c2e538.tar.gz
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>
Diffstat (limited to 'documentation/adt-manual')
-rw-r--r--documentation/adt-manual/adt-prepare.xml13
1 files changed, 7 insertions, 6 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 05a90f0..9f17c21 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -255,15 +255,16 @@
<title>Using BitBake and the Yocto Project Build Tree</title>
<para>
- A final way of installing just the cross-toolchain is to use BitBake to build the
- toolchain within an existing Yocto Project build tree.
- This method does not install the toolchain into the <filename>/opt</filename> directory.
+ A final way of making the cross-toolchain available is to use BitBake
+ to generate the toolchain within an existing Yocto Project build tree.
+ 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
do this separately.
</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>
<listitem><para>Source the environment setup script
<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
command.</note></para></listitem>
<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
<filename>source</filename> the environment setup script and before you run
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
changing out of your working directory.</note>
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
Yocto Project build tree in the <filename>tmp</filename> directory.
Setup script filenames contain the strings <filename>environment-setup</filename>.
OpenPOWER on IntegriCloud