diff options
| author |   Scott Rifenbark <srifenbark@gmail.com> | 2016-03-11 09:35:40 -0800 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-03-11 23:06:07 +0000 |
| commit | 01554725f5f3e248cff951731e9b9fc7794e68ba (patch) | |
| tree | 9716e0e72e8b36517af84a5e68ceb120beee0a6d /documentation/ref-manual | |
| parent | 443846088af9b5df87c7d150f15117647ce8f212 (diff) | |
| download | openembedded-core-contrib-01554725f5f3e248cff951731e9b9fc7794e68ba.tar.gz | |
ref-manual: Updated "Application Development SDK" section.
Applied review comments to the section.
(From yocto-docs rev: 83871d0f6cd996be2d3476bdfc0f2adef9ff52a7)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual')
| -rw-r--r-- | documentation/ref-manual/closer-look.xml | 25 |
1 files changed, 15 insertions, 10 deletions
diff --git a/documentation/ref-manual/closer-look.xml b/documentation/ref-manual/closer-look.xml index 2cbc10605a..e237b3266f 100644 --- a/documentation/ref-manual/closer-look.xml +++ b/documentation/ref-manual/closer-look.xml @@ -1300,9 +1300,14 @@ In the <link linkend='general-yocto-environment-figure'>general Yocto Project Development Environment figure</link>, the output labeled "Application Development SDK" represents an - SDK (standard or extensible). + SDK. + The SDK generation process differs depending on whether you build + a standard SDK + (e.g. <filename>bitbake -c populate_sdk</filename> <replaceable>imagename</replaceable>) + or an extensible SDK + (e.g. <filename>bitbake -c populate_sdk_ext</filename> <replaceable>imagename</replaceable>). This section is going to take a closer look at this output: - <imagedata fileref="figures/sdk.png" align="center" /> + <imagedata fileref="figures/sdk.png" align="center" width="9in" depth="7.25in" /> </para> <para> @@ -1317,8 +1322,8 @@ part because it runs on the SDK machine. You can think of the libraries and headers as the "target" part because they are built for the target hardware. - The setup script is added so that you can initialize the - environment before using the tools. + The environment setup script is added so that you can initialize + the environment before using the tools. </para> <note> @@ -1389,22 +1394,22 @@ 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. + Controls whether or not shared state artifacts are copied + into 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. + Specifies whether or not packagedata will be included in + the extensible SDK 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. + A list of variables not 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 |