summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml12
1 files changed, 10 insertions, 2 deletions
diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml
index 109c601d46..988719d038 100644
--- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml
+++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml
@@ -1560,8 +1560,16 @@
1560 BitBake uses <filename>OVERRIDES</filename> to control 1560 BitBake uses <filename>OVERRIDES</filename> to control
1561 what variables are overridden after BitBake parses 1561 what variables are overridden after BitBake parses
1562 recipes and configuration files. 1562 recipes and configuration files.
1563 You can find more information on how overrides are handled 1563 </para>
1564 in the 1564
1565 <para>
1566 Following is a simple example that uses an overrides
1567 list based on machine architectures:
1568 <literallayout class='monospaced'>
1569 OVERRIDES = "arm:x86:mips:powerpc"
1570 </literallayout>
1571 You can find information on how to use
1572 <filename>OVERRIDES</filename> in the
1565 "<link linkend='conditional-syntax-overrides'>Conditional Syntax (Overrides)</link>" 1573 "<link linkend='conditional-syntax-overrides'>Conditional Syntax (Overrides)</link>"
1566 section. 1574 section.
1567 </para> 1575 </para>