mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-05-30 12:29:55 +00:00
Code Issues Projects Releases Wiki Activity

ref-manual: Drop TUNEABI, TUNEABI_WHITELIST, TUNEABI_OVERRIDE

Browse Source 
Following their removal from openembedded-core

(From yocto-docs rev: bf98f5a15c33e75315cd14e653f253ef078da614)

Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Michael Opdenacker
2022-01-14 15:43:32 +01:00
committed by Richard Purdie
parent 6d0dd8a635
commit d8ddafdbff
1 changed files with 0 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/ref-manual/variables.rst
-34
View File
@@ -8255,40 +8255,6 @@ system and gives an overview of their function and contents.
TUNE_PKGARCH:tune-core2-32 = "core2-32" TUNE_PKGARCH:tune-core2-32 = "core2-32"
:term:`TUNEABI`
An underlying Application Binary Interface (ABI) used by a particular
tuning in a given toolchain layer. Providers that use prebuilt
libraries can use the :term:`TUNEABI`,
:term:`TUNEABI_OVERRIDE`, and
:term:`TUNEABI_WHITELIST` variables to check
compatibility of tunings against their selection of libraries.
If :term:`TUNEABI` is undefined, then every tuning is allowed. See the
:ref:`sanity <ref-classes-sanity>` class to see how the variable is
used.
:term:`TUNEABI_OVERRIDE`
If set, the OpenEmbedded system ignores the
:term:`TUNEABI_WHITELIST` variable.
Providers that use prebuilt libraries can use the
:term:`TUNEABI_OVERRIDE`, :term:`TUNEABI_WHITELIST`, and
:term:`TUNEABI` variables to check compatibility of a
tuning against their selection of libraries.
See the :ref:`sanity <ref-classes-sanity>` class to see how the
variable is used.
:term:`TUNEABI_WHITELIST`
A list of permissible :term:`TUNEABI` values. If
:term:`TUNEABI_WHITELIST` is not set, all tunes are allowed. Providers
that use prebuilt libraries can use the :term:`TUNEABI_WHITELIST`,
:term:`TUNEABI_OVERRIDE`, and :term:`TUNEABI`
variables to check compatibility of a tuning against their selection
of libraries.
See the :ref:`sanity <ref-classes-sanity>` class to see how the
variable is used.
:term:`TUNECONFLICTS[feature]` :term:`TUNECONFLICTS[feature]`
Specifies CPU or Application Binary Interface (ABI) tuning features Specifies CPU or Application Binary Interface (ABI) tuning features
that conflict with feature. that conflict with feature.