To assist existing layers to convert to the new BSP-specific
overrides. Besides failing the parsing of the recipes where it is in
use, we provide a script to automate most of it.
Fixes: #990.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
The overrides ought to allow the filter out execution even for overrides
included during the extension, for this to work we need to postpone it.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
We should be able to use a single MACHINEOVERRIDES_EXTENDER_FILTER_OUT
definition, without an override, to reduce code duplication.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
getVar() has been defaulting to expanding by default for
a long time (2016), thus remove the True option from
getVar() calls with a regex search and replace.
Search & replace made using the following command:
sed -e 's|\(d\.getVar \?\)( \?\([^,()]*\), \?True)|\1(\2)|g' \
-i $(git grep -E 'getVar ?\( ?([^,()]*), ?True\)' \
| cut -d':' -f1 \
| sort -u)
Signed-off-by: André Draszik <andre.draszik@jci.com>
All uses of MACHINEOVERRIDES already include an ':' suffix so we
cannot add it again or we end with a match-all override.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
We need to keep a reference to the original MACHINEOVERRIDES value so
it can be reprocessed as need. This allow the compatibility with
existing BSP's while fixing the complex multilib interactions.
I'd like to record that Richard Purdie was key to solve this issue.
Its implications were beyond my understanding until he guided me and
provided a prototype fix.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
The 'ConfigParsed' event was too early and when we mangled the
MACHINEOVERRIDES using the extender, we ended overriding some values
when using together with multilib.
This fixes the multilib use-case and keep current ones working.
Reported-by: Cristinel Panfir <cristinel.panfir@nxp.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
This reverts commit 65144beb63.
The commit has side effects and must be better investigated. For now,
we are reverting it so we don't cause problems for other use cases.
Change-Id: I63333c974746bd7f95fa7a56153099256e206912
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
The 'ConfigParsed' event was too early and when we mangled the
MACHINEOVERRIDES using the extender, we ended overriding some values
when using together with multilib.
This fixes the multilib use-case and keep current ones working.
Change-Id: I6f1d952dfe2d04fa10229a86763af4ca6b1e601f
Reported-by: Cristinel Panfir <cristinel.panfir@nxp.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
The allow easier enablement of mainline BSP support, we need to allow
for specific overrides to be filtered out, before and during the
extending process.
The new MACHINEOVERRIDES_EXTENDER_FILTER_OUT variable does exactly
this and will be used in a subsequent commit to enable the
'use-mainline-bsp' override.
Change-Id: Ieaec9d5eb27ccc73b7b0097cb365c519978bd080
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
This allow to grouping of different settings for similar platforms.
To use the class, specify, for example:
MACHINEOVERRIDES_EXTENDER_soc = "group1:group2"
Change-Id: I4a7dcd353b8bedf9d8f213827d7de768783c3d5d
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
