| Andrew Geissler | f034379 | 2020-11-18 10:42:21 -0600 | [diff] [blame] | 1 | .. SPDX-License-Identifier: CC-BY-SA-2.0-UK |
| Andrew Geissler | c9f7865 | 2020-09-18 14:11:35 -0500 | [diff] [blame] | 2 | |
| 3 | **************************** |
| 4 | Customizing the Standard SDK |
| 5 | **************************** |
| 6 | |
| 7 | This appendix presents customizations you can apply to the standard SDK. |
| 8 | |
| 9 | Adding Individual Packages to the Standard SDK |
| 10 | ============================================== |
| 11 | |
| 12 | When you build a standard SDK using the ``bitbake -c populate_sdk``, a |
| 13 | default set of packages is included in the resulting SDK. The |
| 14 | :term:`TOOLCHAIN_HOST_TASK` |
| 15 | and |
| 16 | :term:`TOOLCHAIN_TARGET_TASK` |
| 17 | variables control the set of packages adding to the SDK. |
| 18 | |
| 19 | If you want to add individual packages to the toolchain that runs on the |
| 20 | host, simply add those packages to the ``TOOLCHAIN_HOST_TASK`` variable. |
| 21 | Similarly, if you want to add packages to the default set that is part |
| 22 | of the toolchain that runs on the target, add the packages to the |
| 23 | ``TOOLCHAIN_TARGET_TASK`` variable. |
| 24 | |
| 25 | Adding API Documentation to the Standard SDK |
| 26 | ============================================ |
| 27 | |
| 28 | You can include API documentation as well as any other documentation |
| 29 | provided by recipes with the standard SDK by adding "api-documentation" |
| 30 | to the |
| 31 | :term:`DISTRO_FEATURES` |
| 32 | variable: DISTRO_FEATURES_append = " api-documentation" Setting this |
| 33 | variable as shown here causes the OpenEmbedded build system to build the |
| 34 | documentation and then include it in the standard SDK. |