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