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

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: 722836e1af86a46e57dfbeff69a34df5c36fead8)

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 2013-10-24 14:05:38 -07:00 committed by Richard Purdie
parent b963e5d723
commit aa8bad8bac
1 changed files with 31 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -334,37 +334,43 @@
<para> <para>
Follow these steps to generate the toolchain into the Build Directory: Follow these steps to generate the toolchain into the Build Directory:
<orderedlist> <orderedlist>
<listitem><para>Source the environment setup script <listitem><para><emphasis>Set up the Build Environment:</emphasis>
<filename>&OE_INIT_FILE;</filename> located in the Source the OpenEmbedded 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
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
</para></listitem> </para></listitem>
<listitem><para>At this point, you should be sure that the <listitem><para><emphasis>Check your Local Configuration File:</emphasis>
At this point, you should be sure that the
<ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink> variable <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink> variable
in the <filename>local.conf</filename> file found in the in the <filename>local.conf</filename> file found in the
<filename>conf</filename> directory of the Build Directory <filename>conf</filename> directory of the Build Directory
is set for the target architecture. is set for the target architecture.
Comments within the <filename>local.conf</filename> file list the values you Comments within the <filename>local.conf</filename> file
can use for the <filename>MACHINE</filename> variable. list the values you can use for the
<note>You can populate the Build Directory with the cross-toolchains for more <filename>MACHINE</filename> variable.
than a single architecture. <note>
You just need to edit the <filename>MACHINE</filename> variable in the You can populate the Build Directory with the
<filename>local.conf</filename> file and re-run the BitBake cross-toolchains for more than a single architecture.
command.</note></para></listitem> You just need to edit the <filename>MACHINE</filename>
<listitem><para>Run <filename>bitbake meta-ide-support</filename> to complete the variable in the <filename>local.conf</filename> file and
cross-toolchain generation. re-run the BitBake command.
<note>If you change out of your working directory after you </note></para></listitem>
<filename>source</filename> the environment setup script and before you run <listitem><para><emphasis>Generate the Cross-Toolchain:</emphasis>
the BitBake command, the command might not work. Run <filename>bitbake meta-ide-support</filename> to
Be sure to run the BitBake command immediately complete the cross-toolchain generation.
after checking or editing the <filename>local.conf</filename> but without Once the BitBake command finishes, the cross-toolchain is
changing out of your working directory.</note> generated and populated within the Build Directory.
Once the BitBake command finishes, You will notice environment setup files for the
the cross-toolchain is generated and populated within the Build Directory. cross-toolchain that contain the string
You will notice environment setup files for the cross-toolchain in the "<filename>environment-setup</filename>" in the
Build Directory in the <filename>tmp</filename> directory. Build Directory's <filename>tmp</filename> folder.</para>
Setup script filenames contain the strings <filename>environment-setup</filename>.</para> <para>Be aware that when you use this method to install the
<para>Be aware that when you use this method to install the toolchain you still need toolchain, you still need to separately extract and install
to separately extract and install the sysroot filesystem. the sysroot filesystem.
For information on how to do this, see the For information on how to do this, see the
"<link linkend='extracting-the-root-filesystem'>Extracting the Root Filesystem</link>" section. "<link linkend='extracting-the-root-filesystem'>Extracting the Root Filesystem</link>" section.
</para></listitem> </para></listitem>