diff --git a/documentation/overview-manual/overview-manual-concepts.xml b/documentation/overview-manual/overview-manual-concepts.xml index c3e4b457ff..11aadf73e1 100644 --- a/documentation/overview-manual/overview-manual-concepts.xml +++ b/documentation/overview-manual/overview-manual-concepts.xml @@ -2048,24 +2048,26 @@ In the - general Yocto Project Development Environment figure, + general workflow figure, the output labeled "Application Development SDK" represents an SDK. The SDK generation process differs depending on whether you - build a standard SDK (e.g. - bitbake -c populate_sdk imagename) - or an extensible SDK (e.g. - bitbake -c populate_sdk_ext imagename). - This section is going to take a closer look at this output: + build an extensible SDK (e.g. + bitbake -c populate_sdk_ext imagename) + or a standard SDK (e.g. + bitbake -c populate_sdk imagename). + This section takes a closer look at this output: - The specific form of this output is a self-extracting - SDK installer (*.sh) that, when run, - installs the SDK, which consists of a cross-development - toolchain, a set of libraries and headers, and an SDK - environment setup script. + The specific form of this output is a set of files that + includes a self-extracting SDK installer + (*.sh), host and target manifest files, + and files used for SDK testing. + When the SDK installer file is run, it installs the SDK. + The SDK consists of a cross-development toolchain, a set of + libraries and headers, and an SDK environment setup script. Running this installer essentially sets up your cross-development environment. You can think of the cross-toolchain as the "host" @@ -2102,55 +2104,13 @@ - Once built, the SDK installers are written out to the + All the output files for an SDK are written to the deploy/sdk folder inside the Build Directory - as shown in the figure at the beginning of this section. + as shown in the previous figure. 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: - - - DEPLOY_DIR: - Points to the deploy - directory. - - - SDKMACHINE: - Specifies the architecture of the machine - on which the cross-development tools are run to - create packages for the target hardware. - - - SDKIMAGE_FEATURES: - Lists the features to include in the "target" part - of the SDK. - - - TOOLCHAIN_HOST_TASK: - Lists packages that make up the host - part of the SDK (i.e. the part that runs on - the SDKMACHINE). - When you use - bitbake -c populate_sdk imagename - to create the SDK, a set of default packages - apply. - This variable allows you to add more packages. - - - TOOLCHAIN_TARGET_TASK: - Lists packages that make up the target part - of the SDK (i.e. the part built for the - target hardware). - - - SDKPATH: - Defines the default SDK installation path offered - by the installation script. - - - This next list, shows the variables associated with an + The following list shows the variables associated with an extensible SDK: @@ -2166,13 +2126,12 @@ SDK_INCLUDE_PKGDATA: - Specifies whether or not packagedata will be - included in the extensible SDK for all recipes in - the "world" target. + Specifies whether or not packagedata is included in the + extensible SDK for all recipes in the "world" target. SDK_INCLUDE_TOOLCHAIN: - Specifies whether or not the toolchain will be included + Specifies whether or not the toolchain is included when building the extensible SDK. @@ -2194,6 +2153,61 @@ value globally within the extensible SDK configuration. + This next list, shows the variables associated with a standard + SDK: + + + DEPLOY_DIR: + Points to the deploy directory. + + + SDKMACHINE: + Specifies the architecture of the machine on which the + cross-development tools are run to create packages for + the target hardware. + + + SDKIMAGE_FEATURES: + Lists the features to include in the "target" part + of the SDK. + + + TOOLCHAIN_HOST_TASK: + Lists packages that make up the host part of the SDK + (i.e. the part that runs on the + SDKMACHINE). + When you use + bitbake -c populate_sdk imagename + to create the SDK, a set of default packages apply. + This variable allows you to add more packages. + + + TOOLCHAIN_TARGET_TASK: + Lists packages that make up the target part of the SDK + (i.e. the part built for the target hardware). + + + SDKPATH: + Defines the default SDK installation path offered by + the installation script. + + + SDK_HOST_MANIFEST: + Lists all the installed packages that make up the host + part of the SDK. + This variable also plays a minor role for extensible + SDK development as well. + However, it is mainly used for the standard SDK. + + + SDK_TARGET_MANIFEST: + Lists all the installed packages that make up the + target part of the SDK. + This variable also plays a minor role for extensible + SDK development as well. + However, it is mainly used for the standard SDK. + +