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

adt-manual: Added note to indicate ADT is distribution neutral. 

Cleared up some old wording that was confusing the build
system with "Poky".  Also, added a note at the front of the
manual to be clear that the ADT is distribution-neutral.

(From yocto-docs rev: 52d090ab931e5cbeffc612b91c11dbb55db15297)

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-11 12:27:07 -07:00 committed by Richard Purdie
parent 9a51d0a9d5
commit 6b4e25afc4
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
documentation/adt-manual/adt-intro.xml
View File

@ -20,6 +20,11 @@
customize the development packages installation,
how to use command line development for both Autotools-based and Makefile-based projects,
and an introduction to the Eclipse Yocto Plug-in.
<note>
The ADT is distribution-neutral and does not require the Yocto
Project reference distribution, which is called Poky.
This manual, however, uses examples that use the Poky distribution.
</note>
</para>
<section id='adt-intro-section'>
@ -36,7 +41,7 @@
Fundamentally, the ADT consists of the following:
<itemizedlist>
<listitem><para>An architecture-specific cross-toolchain and matching
sysroot both built by the OpenEmbedded build system, which uses Poky.
sysroot both built by the OpenEmbedded build system.
The toolchain and sysroot are based on a metadata configuration and extensions,
which allows you to cross-develop on the host machine for the target hardware.
</para></listitem>
@ -73,7 +78,7 @@
The matching target sysroot contains needed headers and libraries for generating
binaries that run on the target architecture.
The sysroot is based on the target root filesystem image that is built by
the OpenEmbedded build system Poky and uses the same metadata configuration
the OpenEmbedded build system and uses the same metadata configuration
used to build the cross-toolchain.
</para>
</section>