diff options
Diffstat (limited to 'documentation/sdk-manual/sdk-using.xml')
-rw-r--r-- | documentation/sdk-manual/sdk-using.xml | 19 |
1 files changed, 4 insertions, 15 deletions
diff --git a/documentation/sdk-manual/sdk-using.xml b/documentation/sdk-manual/sdk-using.xml index 10089ca3ae..6ddcb45fcf 100644 --- a/documentation/sdk-manual/sdk-using.xml +++ b/documentation/sdk-manual/sdk-using.xml @@ -38,12 +38,6 @@ You can see the directory structure in the "<link linkend='sdk-installed-standard-sdk-directory-structure'>Installed Standard SDK Directory Structure</link>" section. - <note> - You can also find information on how the Yocto Project - OpenEmbedded build system creates an SDK image by looking at the - "<ulink url='&YOCTO_DOCS_REF_URL;#sdk-generation-dev-environment'>SDK Generation</ulink>" - section in the Yocto Project Reference Manual. - </note> </para> </section> @@ -84,12 +78,7 @@ i686 or x86_64. - <replaceable>image_type</replaceable> is a string representing the image you wish to - develop a SDK for use against. The Yocto Project builds - installers for standard SDKs using the following BitBake - command: - - bitbake core-image-sato -c populate_sdk + <replaceable>image_type</replaceable> is the image for which the SDK was built. <replaceable>arch</replaceable> is a string representing the tuned target architecture: @@ -116,11 +105,11 @@ installation directory. <note> You must change the permissions on the toolchain - installer script so that it is executable. - Here is an example: + installer script so that it is executable: <literallayout class='monospaced'> - $ chmod +x poky-glibc-x86_64-core-image-sato-i586-toolchain-2.1.sh + $ chmod +x poky-glibc-x86_64-core-image-sato-i586-toolchain-2.1.sh </literallayout> + This example makes the installation script executable. </note> </para> |