diff options
author | Scott Rifenbark <srifenbark@gmail.com> | 2016-09-13 18:05:31 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-09-23 15:27:34 +0100 |
commit | aba386b92cb1bd926a69f703587b133363374dee (patch) | |
tree | 72a8b0c555d8149b1ac1f0fbb8c52caec742ed89 /documentation/sdk-manual/sdk-appendix-customizing.xml | |
parent | 6cecded9ef1bd09fb7b89ed28c4268c40272665d (diff) | |
download | poky-aba386b92cb1bd926a69f703587b133363374dee.tar.gz |
sdk-manual: Updated SDK workflow
A new command devtool finish has superceded the final commands
in the SDK workflow. I updated the two figures (add and modify)
to reflect this new flow. I also updated the ordered number list
to match reality.
(From yocto-docs rev: 0ba31e730cd748d06eab8d46b38764cda5c4e3bd)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/sdk-manual/sdk-appendix-customizing.xml')
-rw-r--r-- | documentation/sdk-manual/sdk-appendix-customizing.xml | 13 |
1 files changed, 8 insertions, 5 deletions
diff --git a/documentation/sdk-manual/sdk-appendix-customizing.xml b/documentation/sdk-manual/sdk-appendix-customizing.xml index 0695707af3..e8a8b8cc9b 100644 --- a/documentation/sdk-manual/sdk-appendix-customizing.xml +++ b/documentation/sdk-manual/sdk-appendix-customizing.xml | |||
@@ -384,12 +384,15 @@ | |||
384 | 384 | ||
385 | <para> | 385 | <para> |
386 | You can explicitly control whether or not to include the toolchain | 386 | You can explicitly control whether or not to include the toolchain |
387 | when you build and SDK by setting the | 387 | when you build an SDK by setting the |
388 | <ulink url='&YOCTO_DOCS_REF_URL;#var-SDK_INCLUDE_TOOLCHAIN'><filename>SDK_INCLUDE_TOOLCHAIN</filename></ulink> | 388 | <ulink url='&YOCTO_DOCS_REF_URL;#var-SDK_INCLUDE_TOOLCHAIN'><filename>SDK_INCLUDE_TOOLCHAIN</filename></ulink> |
389 | variable. | 389 | variable to "1". |
390 | When you set this variable to "1", you cause the toolchain to be | 390 | In particular, it is useful to include the toolchain when you |
391 | included even when <filename>SDK_EXT_TYPE</filename> is set to | 391 | have set <filename>SDK_EXT_TYPE</filename> to |
392 | "minimal". | 392 | "minimal", which by default, excludes the toolchain. |
393 | Also, it is helpful if you are building a small SDK for use with | ||
394 | an IDE, such as Eclipse, or some other tool where you do not want | ||
395 | to take extra steps to install a toolchain. | ||
393 | </para> | 396 | </para> |
394 | </section> | 397 | </section> |
395 | </appendix> | 398 | </appendix> |