summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
Diffstat (limited to 'documentation')
-rw-r--r--documentation/ref-manual/closer-look.xml79
1 files changed, 79 insertions, 0 deletions
diff --git a/documentation/ref-manual/closer-look.xml b/documentation/ref-manual/closer-look.xml
index 0a6c56c048..9ce92af910 100644
--- a/documentation/ref-manual/closer-look.xml
+++ b/documentation/ref-manual/closer-look.xml
@@ -964,6 +964,85 @@
964 filesystem have correct ownership. 964 filesystem have correct ownership.
965 </note> 965 </note>
966 </section> 966 </section>
967
968 <section id='sdk-generation-dev-environment'>
969 <title>SDK Generation</title>
970
971 <para>
972 The OpenEmbedded build system uses BitBake to generate the
973 Software Development Kit (SDK) installer script and the
974 cross-development environment setup script:
975 <imagedata fileref="figures/sdk-generation.png" align="center" width="6in" depth="7in" />
976 </para>
977
978 <note>
979 For more information on the cross-development toolchain
980 generation, see the
981 "<link linkend='cross-development-toolchain-generation'>Cross-Development Toolchain Generation</link>"
982 section.
983 </note>
984
985 <para>
986 Like image generation, the SDK script process consists of
987 several stages and depends on many variables.
988 The <filename>do_populate_sdk</filename> task uses these
989 key variables to help create the list of packages to actually
990 install:
991 <itemizedlist>
992 <listitem><para><link linkend='var-DEPLOY_DIR'><filename>DEPLOY_DIR</filename></link>:
993 Points to the <filename>deploy</filename>
994 directory.</para></listitem>
995 <listitem><para><link linkend='var-SDKMACHINE'><filename>SDKMACHINE</filename></link>:
996 Specifies the architecture of the machine
997 on which the cross-development tools are run to
998 create packages for the target hardware.
999 </para></listitem>
1000 <listitem><para><link linkend='var-SDKIMAGE_FEATURES'><filename>SDKIMAGE_FEATURES</filename></link>:
1001 Lists the features to include in the "target" part
1002 of the SDK.
1003 </para></listitem>
1004 <listitem><para><link linkend='var-TOOLCHAIN_HOST_TASK'><filename>TOOLCHAIN_HOST_TASK</filename></link>:
1005 Lists packages that make up the host
1006 part of the SDK (i.e. the part that runs on
1007 the <filename>SDKMACHINE</filename>).
1008 When you use
1009 <filename>bitbake -c populate_sdk &lt;imagename&gt;</filename>
1010 to create the SDK, a set of default packages
1011 apply.
1012 This variable allows you to add more packages.
1013 </para></listitem>
1014 <listitem><para><link linkend='var-TOOLCHAIN_TARGET_TASK'><filename>TOOLCHAIN_TARGET_TASK</filename></link>:
1015 Lists packages that make up the target part
1016 of the SDK (i.e. the part built for the
1017 target hardware).
1018 </para></listitem>
1019 </itemizedlist>
1020 </para>
1021
1022 <para>
1023 The <filename>do_populate_sdk</filename> task handles two
1024 parts: a target part and a host part.
1025 The target part is the part built for the target hardware and
1026 includes libraries and headers.
1027 The host part is the part of the SDK that runs on the
1028 <link linkend='var-SDKMACHINE'><filename>SDKMACHINE</filename></link>.
1029 </para>
1030
1031 <para>
1032 Once both parts are constructed, the
1033 <filename>do_populate_sdk</filename> task performs some cleanup
1034 on both parts.
1035 After the cleanup, the task creates a cross-development
1036 environment setup script and any configuration files that
1037 might be needed.
1038 </para>
1039
1040 <para>
1041 The final output of the task is the Cross-development
1042 toolchain installation script (<filename>.sh</filename> file)
1043 and the environment setup script.
1044 </para>
1045 </section>
967 </section> 1046 </section>
968 1047
969 <section id='images-dev-environment'> 1048 <section id='images-dev-environment'>