sdk-manual: Applied 2nd round of review edits.
(From yocto-docs rev: 046b8ed69e0c6403f455e2ec8a0ccc30aea894de) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
6db8cbcbad
commit
54050ffceb
|
@ -18,10 +18,10 @@
|
|||
<para>
|
||||
The extensible SDK primarily consists of a pre-configured copy of
|
||||
the OpenEmbedded build system from which it was produced.
|
||||
Thus, the SDK's configuration is derived using that build system.
|
||||
However, filters such as the following exist that the OpenEmbedded
|
||||
build system applies to <filename>local.conf</filename> and
|
||||
<filename>auto.conf</filename> when these files are present:
|
||||
Thus, the SDK's configuration is derived using that build system and
|
||||
the following filters, which the OpenEmbedded build system applies
|
||||
against <filename>local.conf</filename> and
|
||||
<filename>auto.conf</filename> if they are present:
|
||||
<itemizedlist>
|
||||
<listitem><para>
|
||||
Variables whose values start with "/" are excluded since the
|
||||
|
|
|
@ -54,8 +54,8 @@
|
|||
The extensible SDK installer performs additional tasks as
|
||||
compared to the standard SDK installer.
|
||||
The extensible SDK installer extracts build tools specific
|
||||
to the SDK and the installer also prepares the OpenEmbedded
|
||||
build system.
|
||||
to the SDK and the installer also prepares the internal build
|
||||
system within the SDK.
|
||||
Here is example output for running the extensible SDK
|
||||
installer:
|
||||
<literallayout class='monospaced'>
|
||||
|
@ -255,10 +255,6 @@
|
|||
<para>If you need to take the build output and eventually
|
||||
move it to the target hardware, you would use
|
||||
<filename>devtool build</filename>:
|
||||
<note>
|
||||
You could use <filename>bitbake</filename> to build
|
||||
the recipe as well.
|
||||
</note>
|
||||
<literallayout class='monospaced'>
|
||||
$ devtool build <replaceable>recipe</replaceable>
|
||||
</literallayout></para>
|
||||
|
|
|
@ -38,12 +38,6 @@
|
|||
You can see the directory structure in the
|
||||
"<link linkend='sdk-installed-standard-sdk-directory-structure'>Installed Standard SDK Directory Structure</link>"
|
||||
section.
|
||||
<note>
|
||||
You can also find information on how the Yocto Project
|
||||
OpenEmbedded build system creates an SDK image by looking at the
|
||||
"<ulink url='&YOCTO_DOCS_REF_URL;#sdk-generation-dev-environment'>SDK Generation</ulink>"
|
||||
section in the Yocto Project Reference Manual.
|
||||
</note>
|
||||
</para>
|
||||
</section>
|
||||
|
||||
|
@ -84,12 +78,7 @@
|
|||
|
||||
i686 or x86_64.
|
||||
|
||||
<replaceable>image_type</replaceable> is a string representing the image you wish to
|
||||
develop a SDK for use against. The Yocto Project builds
|
||||
installers for standard SDKs using the following BitBake
|
||||
command:
|
||||
|
||||
bitbake core-image-sato -c populate_sdk
|
||||
<replaceable>image_type</replaceable> is the image for which the SDK was built.
|
||||
|
||||
<replaceable>arch</replaceable> is a string representing the tuned target architecture:
|
||||
|
||||
|
@ -116,11 +105,11 @@
|
|||
installation directory.
|
||||
<note>
|
||||
You must change the permissions on the toolchain
|
||||
installer script so that it is executable.
|
||||
Here is an example:
|
||||
installer script so that it is executable:
|
||||
<literallayout class='monospaced'>
|
||||
$ chmod +x poky-glibc-x86_64-core-image-sato-i586-toolchain-2.1.sh
|
||||
$ chmod +x poky-glibc-x86_64-core-image-sato-i586-toolchain-2.1.sh
|
||||
</literallayout>
|
||||
This example makes the installation script executable.
|
||||
</note>
|
||||
</para>
|
||||
|
||||
|
|
Loading…
Reference in New Issue