summaryrefslogtreecommitdiffstats
path: root/documentation/sdk-manual/sdk-extensible.xml
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 /documentation/sdk-manual/sdk-extensible.xml
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>
Diffstat (limited to 'documentation/sdk-manual/sdk-extensible.xml')
-rw-r--r--documentation/sdk-manual/sdk-extensible.xml8
1 files changed, 2 insertions, 6 deletions
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>