From 81a065bfe8b0d509aa7d9692f304bc34e5b30630 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 19 Jun 2014 18:01:53 +0300 Subject: ref-manual: Added three new tuning variables to glossary. Fixes [YOCTO #5463] New entries for: TUNE_FEATURES AVAILTUNES DEFAULTTUNES (From yocto-docs rev: e56d0027b06171cb547e24a51839cb7f8051e6f2) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/ref-variables.xml | 79 ++++++++++++++++++++++++++++++ 1 file changed, 79 insertions(+) (limited to 'documentation/ref-manual/ref-variables.xml') diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index ae61d29d29..2004a91bec 100644 --- a/documentation/ref-manual/ref-variables.xml +++ b/documentation/ref-manual/ref-variables.xml @@ -251,6 +251,34 @@ + AVAILTUNES + + + The list of defined CPU and Application Binary Interface + (ABI) tunings (i.e. "tunes") available for use by the + OpenEmbedded build system. + + + + The list simply presents the tunes that are available. + Not all tunes may be compatible with a particular + machine configuration, or with each other in a + Multilib + configuration. + + + + To add a tune to the list, be sure to append it with + spaces using the "+=" BitBake operator. + Do not simply replace the list by using the "=" operator. + See the + "Basic Syntax" + section in the BitBake User Manual for more information. + + + + + B @@ -1704,6 +1732,27 @@ + DEFAULTTUNE + + + The default CPU and Application Binary Interface (ABI) + tunings (i.e. the "tune") used by the OpenEmbedded build + system. + The DEFAULTTUNE helps define + TUNE_FEATURES. + + + + The default tune is either implicitly or explicitly set + by the machine + (MACHINE). + However, you can override the setting using available tunes + as defined with + AVAILTUNES. + + + + DEPENDS @@ -8953,6 +9002,36 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" + TUNE_FEATURES + + + Features used to "tune" a compiler for optimal use + given a specific processor. + The features are defined within the tune files and allow + arguments (i.e. TUNE_*ARGS) to be + dynamically generated based on the features. + + + + The OpenEmbedded build system verifies the features + to be sure they are not conflicting and that they are + supported. + + + + The BitBake configuration file + (meta/conf/bitbake.conf) defines + TUNE_FEATURES as follows: + + TUNE_FEATURES ??= "${TUNE_FEATURES_tune-${DEFAULTTUNE}}" + + See the + DEFAULTTUNE + variable for more information. + + + + TUNE_PKGARCH -- cgit v1.2.3-54-g00ecf