mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-05-30 00:20:08 +00:00
Code Issues Projects Releases Wiki Activity

adt-manual: Updates to de-emphasize opt/poky and include sysroot

Browse Source 
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>
This commit is contained in:
Scott Rifenbark
2013-03-01 14:22:44 -06:00
committed by Richard Purdie
parent b7397f3559
commit d8e26e2b9f
2 changed files with 80 additions and 50 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/adt-manual/adt-command.xml
+7 -6
View File
@@ -7,8 +7,8 @@
<para>
Recall that earlier the manual discussed how to use an existing toolchain
tarball that had been installed into <filename>/opt/poky</filename>,
which is outside of the
tarball that had been installed into the default installation
directory, <filename>/opt/poky</filename>, which is outside of the
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>
(see the section "<link linkend='using-an-existing-toolchain-tarball'>Using a Cross-Toolchain Tarball)</link>".
And, that sourcing your architecture-specific environment setup script
@@ -81,13 +81,15 @@
<listitem><para><emphasis>Source the cross-toolchain
environment setup file:</emphasis>
Installation of the cross-toolchain creates a cross-toolchain
environment setup script in <filename>/opt/poky/&lt;release&gt;</filename>.
environment setup script in the directory that the ADT
was installed.
Before you can use the tools to develop your project, you must
source this setup script.
The script begins with the string "environment-setup" and contains
the machine architecture, which is followed by the string
"poky-linux".
Here is an example for an environment setup using the
Here is an example that sources a script from the
default ADT installation directory that uses the
32-bit Intel x86 Architecture and using the
&DISTRO_NAME; Yocto Project release:
<literallayout class='monospaced'>
@@ -158,8 +160,7 @@
For an Autotools-based project, you can use the cross-toolchain by just
passing the appropriate host option to <filename>configure.sh</filename>.
The host option you use is derived from the name of the environment setup
script in <filename>/opt/poky</filename> resulting from installation of the
cross-toolchain tarball.
script found in the directory in which you installed the cross-toolchain.
For example, the host option for an ARM-based target that uses the GNU EABI
is <filename>armv5te-poky-linux-gnueabi</filename>.
You will notice that the name of the script is