summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-10-24 14:05:38 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-11-01 17:09:52 +0000
commit62881f15a8650a9d0f60f5559e5cccbc9b104a7b (patch)
treeecf3310f513e755ac45f3fe89f1eb0758af5c44d
parent443de9269557c56837fec7c781eb4307dd0bf649 (diff)
downloadpoky-62881f15a8650a9d0f60f5559e5cccbc9b104a7b.tar.gz
adt-manual: Edits to "Using BitBake and the Build Directory" section.
I added in some enhancements here: 1. Worded the local build environment setup stuff to include the possibility of memory resident version of BB. 2. Make a better looking list. 3. Dumped the note about changing directories after running your setup script. (From yocto-docs rev: a19874c2b01a38b72fc02e9ae373c335f1dfbef7) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/adt-manual/adt-prepare.xml56
1 files changed, 31 insertions, 25 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index b23bfc05e4..daee1d509f 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -334,37 +334,43 @@
334 <para> 334 <para>
335 Follow these steps to generate the toolchain into the Build Directory: 335 Follow these steps to generate the toolchain into the Build Directory:
336 <orderedlist> 336 <orderedlist>
337 <listitem><para>Source the environment setup script 337 <listitem><para><emphasis>Set up the Build Environment:</emphasis>
338 <filename>&OE_INIT_FILE;</filename> located in the 338 Source the OpenEmbedded build environment setup
339 script (i.e.
340 <ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink>
341 or
342 <ulink url='&YOCTO_DOCS_REF_URL;#structure-memres-core-script'><filename>oe-init-build-env-memres</filename></ulink>)
343 located in the
339 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. 344 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
340 </para></listitem> 345 </para></listitem>
341 <listitem><para>At this point, you should be sure that the 346 <listitem><para><emphasis>Check your Local Configuration File:</emphasis>
347 At this point, you should be sure that the
342 <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink> variable 348 <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink> variable
343 in the <filename>local.conf</filename> file found in the 349 in the <filename>local.conf</filename> file found in the
344 <filename>conf</filename> directory of the Build Directory 350 <filename>conf</filename> directory of the Build Directory
345 is set for the target architecture. 351 is set for the target architecture.
346 Comments within the <filename>local.conf</filename> file list the values you 352 Comments within the <filename>local.conf</filename> file
347 can use for the <filename>MACHINE</filename> variable. 353 list the values you can use for the
348 <note>You can populate the Build Directory with the cross-toolchains for more 354 <filename>MACHINE</filename> variable.
349 than a single architecture. 355 <note>
350 You just need to edit the <filename>MACHINE</filename> variable in the 356 You can populate the Build Directory with the
351 <filename>local.conf</filename> file and re-run the BitBake 357 cross-toolchains for more than a single architecture.
352 command.</note></para></listitem> 358 You just need to edit the <filename>MACHINE</filename>
353 <listitem><para>Run <filename>bitbake meta-ide-support</filename> to complete the 359 variable in the <filename>local.conf</filename> file and
354 cross-toolchain generation. 360 re-run the BitBake command.
355 <note>If you change out of your working directory after you 361 </note></para></listitem>
356 <filename>source</filename> the environment setup script and before you run 362 <listitem><para><emphasis>Generate the Cross-Toolchain:</emphasis>
357 the BitBake command, the command might not work. 363 Run <filename>bitbake meta-ide-support</filename> to
358 Be sure to run the BitBake command immediately 364 complete the cross-toolchain generation.
359 after checking or editing the <filename>local.conf</filename> but without 365 Once the BitBake command finishes, the cross-toolchain is
360 changing out of your working directory.</note> 366 generated and populated within the Build Directory.
361 Once the BitBake command finishes, 367 You will notice environment setup files for the
362 the cross-toolchain is generated and populated within the Build Directory. 368 cross-toolchain that contain the string
363 You will notice environment setup files for the cross-toolchain in the 369 "<filename>environment-setup</filename>" in the
364 Build Directory in the <filename>tmp</filename> directory. 370 Build Directory's <filename>tmp</filename> folder.</para>
365 Setup script filenames contain the strings <filename>environment-setup</filename>.</para> 371 <para>Be aware that when you use this method to install the
366 <para>Be aware that when you use this method to install the toolchain you still need 372 toolchain, you still need to separately extract and install
367 to separately extract and install the sysroot filesystem. 373 the sysroot filesystem.
368 For information on how to do this, see the 374 For information on how to do this, see the
369 "<link linkend='extracting-the-root-filesystem'>Extracting the Root Filesystem</link>" section. 375 "<link linkend='extracting-the-root-filesystem'>Extracting the Root Filesystem</link>" section.
370 </para></listitem> 376 </para></listitem>