diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2013-03-01 14:22:44 -0600 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-03-02 12:57:21 +0000 |
commit | d8e26e2b9f8b622d0cef3d3d1392dd0917343ded (patch) | |
tree | 7950c822e1a00ae43cf3e5e7230df8b5c9f3f743 /documentation/adt-manual/adt-command.xml | |
parent | b7397f3559b2ca86943594122b3cf008e50f80a2 (diff) | |
download | poky-d8e26e2b9f8b622d0cef3d3d1392dd0917343ded.tar.gz |
adt-manual: Updates to de-emphasize opt/poky and include sysroot
Fixes YOCTO #2645
Several changes to make sure that the default toolchain directory
(opt/poky) is understood as the default. I changed some wordings
to call it out as the default. Some examples I left alone as they
used /opt/poky but I clearly indicated that the example was using
the default installation directory.
I also updated the note in the manual that talks about alternatively
building the toolchain installer. Previously, it mentioned two
methods. I have added the third and most significant method that
uses bitbake image -c populate_sdk. This method creates a toolchain
installer that contains the matching sysroot.
(From yocto-docs rev: 2e5eeb7e0c9aa448149cc369572b31dbc1603e28)
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-command.xml')
-rw-r--r-- | documentation/adt-manual/adt-command.xml | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/documentation/adt-manual/adt-command.xml b/documentation/adt-manual/adt-command.xml index e5b2cdb420..18bfb8a829 100644 --- a/documentation/adt-manual/adt-command.xml +++ b/documentation/adt-manual/adt-command.xml | |||
@@ -7,8 +7,8 @@ | |||
7 | 7 | ||
8 | <para> | 8 | <para> |
9 | Recall that earlier the manual discussed how to use an existing toolchain | 9 | Recall that earlier the manual discussed how to use an existing toolchain |
10 | tarball that had been installed into <filename>/opt/poky</filename>, | 10 | tarball that had been installed into the default installation |
11 | which is outside of the | 11 | directory, <filename>/opt/poky</filename>, which is outside of the |
12 | <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink> | 12 | <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink> |
13 | (see the section "<link linkend='using-an-existing-toolchain-tarball'>Using a Cross-Toolchain Tarball)</link>". | 13 | (see the section "<link linkend='using-an-existing-toolchain-tarball'>Using a Cross-Toolchain Tarball)</link>". |
14 | And, that sourcing your architecture-specific environment setup script | 14 | And, that sourcing your architecture-specific environment setup script |
@@ -81,13 +81,15 @@ | |||
81 | <listitem><para><emphasis>Source the cross-toolchain | 81 | <listitem><para><emphasis>Source the cross-toolchain |
82 | environment setup file:</emphasis> | 82 | environment setup file:</emphasis> |
83 | Installation of the cross-toolchain creates a cross-toolchain | 83 | Installation of the cross-toolchain creates a cross-toolchain |
84 | environment setup script in <filename>/opt/poky/<release></filename>. | 84 | environment setup script in the directory that the ADT |
85 | was installed. | ||
85 | Before you can use the tools to develop your project, you must | 86 | Before you can use the tools to develop your project, you must |
86 | source this setup script. | 87 | source this setup script. |
87 | The script begins with the string "environment-setup" and contains | 88 | The script begins with the string "environment-setup" and contains |
88 | the machine architecture, which is followed by the string | 89 | the machine architecture, which is followed by the string |
89 | "poky-linux". | 90 | "poky-linux". |
90 | Here is an example for an environment setup using the | 91 | Here is an example that sources a script from the |
92 | default ADT installation directory that uses the | ||
91 | 32-bit Intel x86 Architecture and using the | 93 | 32-bit Intel x86 Architecture and using the |
92 | &DISTRO_NAME; Yocto Project release: | 94 | &DISTRO_NAME; Yocto Project release: |
93 | <literallayout class='monospaced'> | 95 | <literallayout class='monospaced'> |
@@ -158,8 +160,7 @@ | |||
158 | For an Autotools-based project, you can use the cross-toolchain by just | 160 | For an Autotools-based project, you can use the cross-toolchain by just |
159 | passing the appropriate host option to <filename>configure.sh</filename>. | 161 | passing the appropriate host option to <filename>configure.sh</filename>. |
160 | The host option you use is derived from the name of the environment setup | 162 | The host option you use is derived from the name of the environment setup |
161 | script in <filename>/opt/poky</filename> resulting from installation of the | 163 | script found in the directory in which you installed the cross-toolchain. |
162 | cross-toolchain tarball. | ||
163 | For example, the host option for an ARM-based target that uses the GNU EABI | 164 | For example, the host option for an ARM-based target that uses the GNU EABI |
164 | is <filename>armv5te-poky-linux-gnueabi</filename>. | 165 | is <filename>armv5te-poky-linux-gnueabi</filename>. |
165 | You will notice that the name of the script is | 166 | You will notice that the name of the script is |