summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2016-03-22 09:49:33 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-03-23 21:56:10 +0000
commit54050ffceb96b8ad8c089f6612e094a367a4edc8 (patch)
treeba5d514d845fd8d88324a9118a648d4c753c0cf6
parent6db8cbcbadd0019fa5d879c6cc727a2819341b07 (diff)
downloadpoky-54050ffceb96b8ad8c089f6612e094a367a4edc8.tar.gz
sdk-manual: Applied 2nd round of review edits.
(From yocto-docs rev: 046b8ed69e0c6403f455e2ec8a0ccc30aea894de) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/sdk-manual/sdk-appendix-customizing.xml8
-rw-r--r--documentation/sdk-manual/sdk-extensible.xml8
-rw-r--r--documentation/sdk-manual/sdk-using.xml19
3 files changed, 10 insertions, 25 deletions
diff --git a/documentation/sdk-manual/sdk-appendix-customizing.xml b/documentation/sdk-manual/sdk-appendix-customizing.xml
index 7a438725b6..d38320f8bb 100644
--- a/documentation/sdk-manual/sdk-appendix-customizing.xml
+++ b/documentation/sdk-manual/sdk-appendix-customizing.xml
@@ -18,10 +18,10 @@
18 <para> 18 <para>
19 The extensible SDK primarily consists of a pre-configured copy of 19 The extensible SDK primarily consists of a pre-configured copy of
20 the OpenEmbedded build system from which it was produced. 20 the OpenEmbedded build system from which it was produced.
21 Thus, the SDK's configuration is derived using that build system. 21 Thus, the SDK's configuration is derived using that build system and
22 However, filters such as the following exist that the OpenEmbedded 22 the following filters, which the OpenEmbedded build system applies
23 build system applies to <filename>local.conf</filename> and 23 against <filename>local.conf</filename> and
24 <filename>auto.conf</filename> when these files are present: 24 <filename>auto.conf</filename> if they are present:
25 <itemizedlist> 25 <itemizedlist>
26 <listitem><para> 26 <listitem><para>
27 Variables whose values start with "/" are excluded since the 27 Variables whose values start with "/" are excluded since the
diff --git a/documentation/sdk-manual/sdk-extensible.xml b/documentation/sdk-manual/sdk-extensible.xml
index 58d2aec977..e43c98ecee 100644
--- a/documentation/sdk-manual/sdk-extensible.xml
+++ b/documentation/sdk-manual/sdk-extensible.xml
@@ -54,8 +54,8 @@
54 The extensible SDK installer performs additional tasks as 54 The extensible SDK installer performs additional tasks as
55 compared to the standard SDK installer. 55 compared to the standard SDK installer.
56 The extensible SDK installer extracts build tools specific 56 The extensible SDK installer extracts build tools specific
57 to the SDK and the installer also prepares the OpenEmbedded 57 to the SDK and the installer also prepares the internal build
58 build system. 58 system within the SDK.
59 Here is example output for running the extensible SDK 59 Here is example output for running the extensible SDK
60 installer: 60 installer:
61 <literallayout class='monospaced'> 61 <literallayout class='monospaced'>
@@ -255,10 +255,6 @@
255 <para>If you need to take the build output and eventually 255 <para>If you need to take the build output and eventually
256 move it to the target hardware, you would use 256 move it to the target hardware, you would use
257 <filename>devtool build</filename>: 257 <filename>devtool build</filename>:
258 <note>
259 You could use <filename>bitbake</filename> to build
260 the recipe as well.
261 </note>
262 <literallayout class='monospaced'> 258 <literallayout class='monospaced'>
263 $ devtool build <replaceable>recipe</replaceable> 259 $ devtool build <replaceable>recipe</replaceable>
264 </literallayout></para> 260 </literallayout></para>
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 @@
38 You can see the directory structure in the 38 You can see the directory structure in the
39 "<link linkend='sdk-installed-standard-sdk-directory-structure'>Installed Standard SDK Directory Structure</link>" 39 "<link linkend='sdk-installed-standard-sdk-directory-structure'>Installed Standard SDK Directory Structure</link>"
40 section. 40 section.
41 <note>
42 You can also find information on how the Yocto Project
43 OpenEmbedded build system creates an SDK image by looking at the
44 "<ulink url='&YOCTO_DOCS_REF_URL;#sdk-generation-dev-environment'>SDK Generation</ulink>"
45 section in the Yocto Project Reference Manual.
46 </note>
47 </para> 41 </para>
48</section> 42</section>
49 43
@@ -84,12 +78,7 @@
84 78
85 i686 or x86_64. 79 i686 or x86_64.
86 80
87 <replaceable>image_type</replaceable> is a string representing the image you wish to 81 <replaceable>image_type</replaceable> is the image for which the SDK was built.
88 develop a SDK for use against. The Yocto Project builds
89 installers for standard SDKs using the following BitBake
90 command:
91
92 bitbake core-image-sato -c populate_sdk
93 82
94 <replaceable>arch</replaceable> is a string representing the tuned target architecture: 83 <replaceable>arch</replaceable> is a string representing the tuned target architecture:
95 84
@@ -116,11 +105,11 @@
116 installation directory. 105 installation directory.
117 <note> 106 <note>
118 You must change the permissions on the toolchain 107 You must change the permissions on the toolchain
119 installer script so that it is executable. 108 installer script so that it is executable:
120 Here is an example:
121 <literallayout class='monospaced'> 109 <literallayout class='monospaced'>
122 $ chmod +x poky-glibc-x86_64-core-image-sato-i586-toolchain-2.1.sh 110 $ chmod +x poky-glibc-x86_64-core-image-sato-i586-toolchain-2.1.sh
123 </literallayout> 111 </literallayout>
112 This example makes the installation script executable.
124 </note> 113 </note>
125 </para> 114 </para>
126 115