dev-manual, mega-manual: Updated "Application Development SDK" section.

I updated the figure for this section to include some stuff
for the extensible SDK.  I updated the text supporting the
figure to cover the different SDKs and the different SDK
variable sets.

(From yocto-docs rev: 5aafab3e2e841293ddba45dfd8683cbdc223ed7c)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2016-03-09 11:55:11 -08:00 committed by Richard Purdie
parent 357aa3322e
commit d9fc04b47c
3 changed files with 39 additions and 11 deletions

Binary file not shown.

Before

Width:  |  Height:  |  Size: 34 KiB

After

Width:  |  Height:  |  Size: 66 KiB

View File

@ -1300,9 +1300,9 @@
In the In the
<link linkend='general-yocto-environment-figure'>general Yocto Project Development Environment figure</link>, <link linkend='general-yocto-environment-figure'>general Yocto Project Development Environment figure</link>,
the output labeled "Application Development SDK" represents an the output labeled "Application Development SDK" represents an
SDK. SDK (standard or extensible).
This section is going to take a closer look at this output: This section is going to take a closer look at this output:
<imagedata fileref="figures/sdk.png" align="center" width="6in" depth="5in" scalefit="100" /> <imagedata fileref="figures/sdk.png" align="center" />
</para> </para>
<para> <para>
@ -1325,12 +1325,8 @@
<para> <para>
The Yocto Project supports several methods by which you can The Yocto Project supports several methods by which you can
set up this cross-development environment. set up this cross-development environment.
These methods include downloading pre-built SDK installers, These methods include downloading pre-built SDK installers
building and installing your own SDK installer, or running or building and installing your own SDK installer.
an Application Development Toolkit (ADT) installer to
install not just cross-development toolchains
but also additional tools to help in this type of
development.
</para> </para>
<para> <para>
@ -1340,8 +1336,7 @@
section. section.
For information on setting up a cross-development For information on setting up a cross-development
environment, see the environment, see the
"<ulink url='&YOCTO_DOCS_ADT_URL;#installing-the-adt'>Installing the ADT and Toolchains</ulink>" <ulink url='&YOCTO_DOCS_SDK_URL;#sdk-manual'>Yocto Project Software Development Kit (SDK) Developer's Guide</ulink>.
section in the Yocto Project Application Developer's Guide.
</para> </para>
</note> </note>
@ -1350,7 +1345,10 @@
<filename>deploy/sdk</filename> folder inside the <filename>deploy/sdk</filename> folder inside the
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink> <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>
as shown in the figure at the beginning of this section. as shown in the figure at the beginning of this section.
Several variables exist that help configure these files: Depending on the type of SDK, several variables exist that help
configure these files.
The following list shows the variables associated with a standard
SDK:
<itemizedlist> <itemizedlist>
<listitem><para><link linkend='var-DEPLOY_DIR'><filename>DEPLOY_DIR</filename></link>: <listitem><para><link linkend='var-DEPLOY_DIR'><filename>DEPLOY_DIR</filename></link>:
Points to the <filename>deploy</filename> Points to the <filename>deploy</filename>
@ -1384,6 +1382,36 @@
installation script. installation script.
</para></listitem> </para></listitem>
</itemizedlist> </itemizedlist>
This next list, shows the variables associated with an extensible
SDK:
<itemizedlist>
<listitem><para><link linkend='var-DEPLOY_DIR'><filename>DEPLOY_DIR</filename></link>:
Points to the <filename>deploy</filename> directory.
</para></listitem>
<listitem><para><link linkend='var-SDK_EXT_TYPE'><filename>SDK_EXT_TYPE</filename></link>:
Specifies the required shared state artifacts for the
extensible SDK.
By default, all required shared state artifacts are copied
into the SDK.
</para></listitem>
<listitem><para><link linkend='var-SDK_INCLUDE_PKGDATA'><filename>SDK_INCLUDE_PKGDATA</filename></link>:
Includes as part of the extensible SDK the packagedata for
all recipes in the "world" target.
</para></listitem>
<listitem><para><link linkend='var-SDK_LOCAL_CONF_WHITELIST'><filename>SDK_LOCAL_CONF_WHITELIST</filename></link>:
A list of variables allowed through from the build system
configuration into the extensible SDK configuration.
</para></listitem>
<listitem><para><link linkend='var-SDK_LOCAL_CONF_BLACKLIST'><filename>SDK_LOCAL_CONF_BLACKLIST</filename></link>:
A list of variables allowed through from the build system
configuration into the extensible SDK configuration.
</para></listitem>
<listitem><para><link linkend='var-SDK_INHERIT_BLACKLIST'><filename>SDK_INHERIT_BLACKLIST</filename></link>:
A list of classes to remove from the
<link linkend='var-INHERIT'><filename>INHERIT</filename></link>
value globally within the extensible SDK configuration.
</para></listitem>
</itemizedlist>
</para> </para>
</section> </section>

Binary file not shown.

Before

Width:  |  Height:  |  Size: 34 KiB

After

Width:  |  Height:  |  Size: 66 KiB