summaryrefslogtreecommitdiffstats
path: root/documentation/adt-manual/adt-prepare.xml
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/adt-prepare.xml
parent73411842a6c71a50790ad7895484fcac3b97ef1d (diff)
downloadpoky-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/adt-prepare.xml')
-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 05a90f0846..9f17c213cc 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -255,15 +255,16 @@
255 <title>Using BitBake and the Yocto Project Build Tree</title> 255 <title>Using BitBake and the Yocto Project Build Tree</title>
256 256
257 <para> 257 <para>
258 A final way of installing just the cross-toolchain is to use BitBake to build the 258 A final way of making the cross-toolchain available is to use BitBake
259 toolchain within an existing Yocto Project build tree. 259 to generate the toolchain within an existing Yocto Project build tree.
260 This method does not install the toolchain into the <filename>/opt</filename> directory. 260 This method does not install the toolchain into the
261 <filename>/opt</filename> directory.
261 As with the previous method, if you need to install the target sysroot, you must 262 As with the previous method, if you need to install the target sysroot, you must
262 do this separately. 263 do this separately.
263 </para> 264 </para>
264 265
265 <para> 266 <para>
266 Follow these steps to build and install the toolchain into the build tree: 267 Follow these steps to generate the toolchain into the build tree:
267 <orderedlist> 268 <orderedlist>
268 <listitem><para>Source the environment setup script 269 <listitem><para>Source the environment setup script
269 <filename>oe-init-build-env</filename> located in the Yocto Project 270 <filename>oe-init-build-env</filename> located in the Yocto Project
@@ -281,7 +282,7 @@
281 <filename>local.conf</filename> file and re-run the BitBake 282 <filename>local.conf</filename> file and re-run the BitBake
282 command.</note></para></listitem> 283 command.</note></para></listitem>
283 <listitem><para>Run <filename>bitbake meta-ide-support</filename> to complete the 284 <listitem><para>Run <filename>bitbake meta-ide-support</filename> to complete the
284 cross-toolchain installation. 285 cross-toolchain generation.
285 <note>If you change out of your working directory after you 286 <note>If you change out of your working directory after you
286 <filename>source</filename> the environment setup script and before you run 287 <filename>source</filename> the environment setup script and before you run
287 the <filename>bitbake</filename> command, the command might not work. 288 the <filename>bitbake</filename> command, the command might not work.
@@ -289,7 +290,7 @@
289 after checking or editing the <filename>local.conf</filename> but without 290 after checking or editing the <filename>local.conf</filename> but without
290 changing out of your working directory.</note> 291 changing out of your working directory.</note>
291 Once the <filename>bitbake</filename> command finishes, 292 Once the <filename>bitbake</filename> command finishes,
292 the tarball for the cross-toolchain is generated within the Yocto Project build tree. 293 the cross-toolchain is generated and populated within the Yocto Project build tree.
293 You will notice environment setup files for the cross-toolchain in the 294 You will notice environment setup files for the cross-toolchain in the
294 Yocto Project build tree in the <filename>tmp</filename> directory. 295 Yocto Project build tree in the <filename>tmp</filename> directory.
295 Setup script filenames contain the strings <filename>environment-setup</filename>. 296 Setup script filenames contain the strings <filename>environment-setup</filename>.