3 files changed, 7 insertions, 34 deletions
diff --git a/documentation/mega-manual/figures/sdk-generation.png b/documentation/mega-manual/figures/sdk-generation.png
index 9e7fd9a75d..c37e2748ca 100644
--- a/documentation/mega-manual/figures/sdk-generation.png
+++ b/documentation/mega-manual/figures/sdk-generation.png
Binary files differ
diff --git a/documentation/ref-manual/closer-look.xml b/documentation/ref-manual/closer-look.xml
index 0947340c07..eccf97698a 100644
--- a/documentation/ref-manual/closer-look.xml
+++ b/documentation/ref-manual/closer-look.xml
@@ -981,8 +981,7 @@
            <para>
                The OpenEmbedded build system uses BitBake to generate the
-                Software Development Kit (SDK) installer script and the
+                Software Development Kit (SDK) installer script:
-                cross-development environment setup script:
                <imagedata fileref="figures/sdk-generation.png" align="center" width="6in" depth="7in" />
            </para>
@@ -998,36 +997,10 @@
                several stages and depends on many variables.
                The <filename>do_populate_sdk</filename> task uses these
                key variables to help create the list of packages to actually
-                install:
+                install.
-                <itemizedlist>
+                For information on the variables listed in the figure, see the
-                    <listitem><para><link linkend='var-DEPLOY_DIR'><filename>DEPLOY_DIR</filename></link>:
+                "<link linkend='sdk-dev-environment'>Application Development SDK</link>"
-                        Points to the <filename>deploy</filename>
+                section.
-                        directory.</para></listitem>
-                    <listitem><para><link linkend='var-SDKMACHINE'><filename>SDKMACHINE</filename></link>:
-                        Specifies the architecture of the machine
-                        on which the cross-development tools are run to
-                        create packages for the target hardware.
-                        </para></listitem>
-                    <listitem><para><link linkend='var-SDKIMAGE_FEATURES'><filename>SDKIMAGE_FEATURES</filename></link>:
-                        Lists the features to include in the "target" part
-                        of the SDK.
-                        </para></listitem>
-                    <listitem><para><link linkend='var-TOOLCHAIN_HOST_TASK'><filename>TOOLCHAIN_HOST_TASK</filename></link>:
-                        Lists packages that make up the host
-                        part of the SDK (i.e. the part that runs on
-                        the <filename>SDKMACHINE</filename>).
-                        When you use
-                        <filename>bitbake -c populate_sdk &lt;imagename&gt;</filename>
-                        to create the SDK, a set of default packages
-                        apply.
-                        This variable allows you to add more packages.
-                        </para></listitem>
-                    <listitem><para><link linkend='var-TOOLCHAIN_TARGET_TASK'><filename>TOOLCHAIN_TARGET_TASK</filename></link>:
-                        Lists packages that make up the target part
-                        of the SDK (i.e. the part built for the
-                        target hardware).
-                        </para></listitem>
-                </itemizedlist>
            </para>
            <para>
@@ -1050,8 +1023,8 @@
            <para>
                The final output of the task is the Cross-development
-                toolchain installation script (<filename>.sh</filename> file)
+                toolchain installation script (<filename>.sh</filename> file),
-                and the environment setup script.
+                which includes the environment setup script.
            </para>
        </section>
    </section>
diff --git a/documentation/ref-manual/figures/sdk-generation.png b/documentation/ref-manual/figures/sdk-generation.png
index 9e7fd9a75d..c37e2748ca 100644
--- a/documentation/ref-manual/figures/sdk-generation.png
+++ b/documentation/ref-manual/figures/sdk-generation.png
Binary files differ

diff --git a/documentation/mega-manual/figures/sdk-generation.png b/documentation/mega-manual/figures/sdk-generation.png index 9e7fd9a75d..c37e2748ca 100644 --- a/documentation/mega-manual/figures/sdk-generation.png +++ b/documentation/mega-manual/figures/sdk-generation.png
Binary files differ


diff --git a/documentation/ref-manual/closer-look.xml b/documentation/ref-manual/closer-look.xml index 0947340c07..eccf97698a 100644 --- a/documentation/ref-manual/closer-look.xml +++ b/documentation/ref-manual/closer-look.xml
@@ -981,8 +981,7 @@
981		981
982	<para>	982	<para>
983	The OpenEmbedded build system uses BitBake to generate the	983	The OpenEmbedded build system uses BitBake to generate the
984	Software Development Kit (SDK) installer script and the	984	Software Development Kit (SDK) installer script:
985	cross-development environment setup script:
986	<imagedata fileref="figures/sdk-generation.png" align="center" width="6in" depth="7in" />	985	<imagedata fileref="figures/sdk-generation.png" align="center" width="6in" depth="7in" />
987	</para>	986	</para>
988		987
@@ -998,36 +997,10 @@
998	several stages and depends on many variables.	997	several stages and depends on many variables.
999	The <filename>do_populate_sdk</filename> task uses these	998	The <filename>do_populate_sdk</filename> task uses these
1000	key variables to help create the list of packages to actually	999	key variables to help create the list of packages to actually
1001	install:	1000	install.
1002	<itemizedlist>	1001	For information on the variables listed in the figure, see the
1003	<listitem><para><link linkend='var-DEPLOY_DIR'><filename>DEPLOY_DIR</filename></link>:	1002	"<link linkend='sdk-dev-environment'>Application Development SDK</link>"
1004	Points to the <filename>deploy</filename>	1003	section.
1005	directory.</para></listitem>
1006	<listitem><para><link linkend='var-SDKMACHINE'><filename>SDKMACHINE</filename></link>:
1007	Specifies the architecture of the machine
1008	on which the cross-development tools are run to
1009	create packages for the target hardware.
1010	</para></listitem>
1011	<listitem><para><link linkend='var-SDKIMAGE_FEATURES'><filename>SDKIMAGE_FEATURES</filename></link>:
1012	Lists the features to include in the "target" part
1013	of the SDK.
1014	</para></listitem>
1015	<listitem><para><link linkend='var-TOOLCHAIN_HOST_TASK'><filename>TOOLCHAIN_HOST_TASK</filename></link>:
1016	Lists packages that make up the host
1017	part of the SDK (i.e. the part that runs on
1018	the <filename>SDKMACHINE</filename>).
1019	When you use
1020	<filename>bitbake -c populate_sdk <imagename></filename>
1021	to create the SDK, a set of default packages
1022	apply.
1023	This variable allows you to add more packages.
1024	</para></listitem>
1025	<listitem><para><link linkend='var-TOOLCHAIN_TARGET_TASK'><filename>TOOLCHAIN_TARGET_TASK</filename></link>:
1026	Lists packages that make up the target part
1027	of the SDK (i.e. the part built for the
1028	target hardware).
1029	</para></listitem>
1030	</itemizedlist>
1031	</para>	1004	</para>
1032		1005
1033	<para>	1006	<para>
@@ -1050,8 +1023,8 @@
1050		1023
1051	<para>	1024	<para>
1052	The final output of the task is the Cross-development	1025	The final output of the task is the Cross-development
1053	toolchain installation script (<filename>.sh</filename> file)	1026	toolchain installation script (<filename>.sh</filename> file),
1054	and the environment setup script.	1027	which includes the environment setup script.
1055	</para>	1028	</para>
1056	</section>	1029	</section>
1057	</section>	1030	</section>


diff --git a/documentation/ref-manual/figures/sdk-generation.png b/documentation/ref-manual/figures/sdk-generation.png index 9e7fd9a75d..c37e2748ca 100644 --- a/documentation/ref-manual/figures/sdk-generation.png +++ b/documentation/ref-manual/figures/sdk-generation.png
Binary files differ