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