diff options
| -rw-r--r-- | documentation/adt-manual/adt-prepare.xml | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml index 4df10bf..c6bfd49 100644 --- a/documentation/adt-manual/adt-prepare.xml +++ b/documentation/adt-manual/adt-prepare.xml @@ -91,16 +91,16 @@ <para> If you use BitBake to generate the ADT Installer tarball, you must <filename>source</filename> the environment setup script - (<filename>&OE_INIT_FILE;</filename>) located - in the Source Directory before running the <filename>bitbake</filename> - command that creates the tarball. + (<ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink>) + located in the Source Directory before running the + BitBake command that creates the tarball. </para> <para> The following example commands download the Poky tarball, set up the <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>, set up the environment while also creating the default Build Directory, - and run the <filename>bitbake</filename> command that results in the tarball + and run the BitBake command that results in the tarball <filename>~/yocto-project/build/tmp/deploy/sdk/adt_installer.tar.bz2</filename>: <literallayout class='monospaced'> $ cd ~ @@ -293,7 +293,7 @@ variable is correctly set if you are building a toolchain for an architecture that differs from your current development host machine.</para> - <para>When the <filename>bitbake</filename> command + <para>When the BitBake command completes, the toolchain installer will be in <filename>tmp/deploy/sdk</filename> in the Build Directory.</para> @@ -326,7 +326,7 @@ A final way of making the cross-toolchain available is to use BitBake to generate the toolchain within an existing <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>. - This method does not install the toolchain into the + This method does not install the toolchain into the default <filename>/opt</filename> directory. As with the previous method, if you need to install the target sysroot, you must do that separately as well. @@ -355,11 +355,11 @@ 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. - Be sure to run the <filename>bitbake</filename> command immediately + the BitBake command, the command might not work. + Be sure to run the BitBake command immediately 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, + Once the BitBake command finishes, the cross-toolchain is generated and populated within the Build Directory. You will notice environment setup files for the cross-toolchain in the Build Directory in the <filename>tmp</filename> directory. @@ -393,7 +393,7 @@ <para> Be sure to run the environment setup script that matches the architecture for which you are developing. - Environment setup scripts begin with the string “<filename>environment-setup</filename>” + Environment setup scripts begin with the string "<filename>environment-setup</filename>" and include as part of their name the architecture. For example, the toolchain environment setup script for a 64-bit IA-based architecture installed in the default installation directory @@ -442,8 +442,8 @@ <para> If you are planning on developing against your image and you are not building or using one of the Yocto Project development images - (e.g. core-image-*-dev), you must be sure to include the development - packages as part of your image recipe. + (e.g. <filename>core-image-*-dev</filename>), you must be sure to + include the development packages as part of your image recipe. </para> <para> |
