| Brad Bishop | 37a0e4d | 2017-12-04 01:01:44 -0500 | [diff] [blame] | 1 | <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" | 
 | 2 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" | 
 | 3 | [<!ENTITY % poky SYSTEM "../poky.ent"> %poky; ] > | 
 | 4 |  | 
 | 5 | <appendix id='sdk-appendix-customizing-standard'> | 
 | 6 |  | 
 | 7 | <title>Customizing the Standard SDK</title> | 
 | 8 |  | 
 | 9 | <para> | 
 | 10 |     This appendix presents customizations you can apply to the standard SDK. | 
 | 11 | </para> | 
 | 12 |  | 
 | 13 | <section id='sdk-adding-individual-packages'> | 
 | 14 |     <title>Adding Individual Packages to the Standard SDK</title> | 
 | 15 |  | 
 | 16 |     <para> | 
 | 17 |          When you build a standard SDK using the | 
 | 18 |          <filename>bitbake -c populate_sdk</filename>, a default set of | 
 | 19 |          packages is included in the resulting SDK. | 
 | 20 |          The | 
 | 21 |          <ulink url='&YOCTO_DOCS_REF_URL;#var-TOOLCHAIN_HOST_TASK'><filename>TOOLCHAIN_HOST_TASK</filename></ulink> | 
 | 22 |          and | 
 | 23 |          <ulink url='&YOCTO_DOCS_REF_URL;#var-TOOLCHAIN_TARGET_TASK'><filename>TOOLCHAIN_TARGET_TASK</filename></ulink> | 
 | 24 |          variables control the set of packages adding to the SDK. | 
 | 25 |     </para> | 
 | 26 |  | 
 | 27 |     <para> | 
 | 28 |         If you want to add individual packages to the toolchain that runs on | 
 | 29 |         the host, simply add those packages to the | 
 | 30 |         <filename>TOOLCHAIN_HOST_TASK</filename> variable. | 
 | 31 |         Similarly, if you want to add packages to the default set that is | 
 | 32 |         part of the toolchain that runs on the target, add the packages to the | 
 | 33 |         <filename>TOOLCHAIN_TARGET_TASK</filename> variable. | 
 | 34 |     </para> | 
 | 35 | </section> | 
 | 36 |  | 
 | 37 | <section id='adding-api-documentation-to-the-standard-sdk'> | 
 | 38 |     <title>Adding API Documentation to the Standard SDK</title> | 
 | 39 |  | 
 | 40 |     <para> | 
 | 41 |         You can include API documentation as well as any other | 
 | 42 |         documentation provided by recipes with the standard SDK by | 
 | 43 |         adding "api-documentation" to the | 
 | 44 |         <ulink url='&YOCTO_DOCS_REF_URL;#var-DISTRO_FEATURES'><filename>DISTRO_FEATURES</filename></ulink> | 
 | 45 |         variable: | 
 | 46 |         <literallayout class='monospaced'> | 
 | 47 |      DISTRO_FEATURES_append = " api-documentation" | 
 | 48 |         </literallayout> | 
 | 49 |         Setting this variable as shown here causes the OpenEmbedded build | 
 | 50 |         system to build the documentation and then include it in the standard | 
 | 51 |         SDK. | 
 | 52 |     </para> | 
 | 53 | </section> | 
 | 54 |  | 
 | 55 | </appendix> | 
 | 56 | <!-- | 
 | 57 | vim: expandtab tw=80 ts=4 | 
 | 58 | --> |