summaryrefslogtreecommitdiffstats
path: root/recipes-extended/xen/xen-arch.inc
Commit message (Collapse)AuthorAgeFilesLines
* Remove True option to getVar callsPaul Barker2017-01-031-1/+1
| | | | | | | getVar() now defaults to expanding by default. Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* xen-arch: add explicit expansion parameterBruce Ashfield2016-02-221-1/+1
| | | | | | | To avoid parse errors with oe-core master, we need to expliictly pass the expansion parameter to getVar. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* xen: avoid parse time errors for non-xen-archsChristopher Larson2015-03-171-1/+1
| | | | | | | | | | | | | | | XEN_TARGET_ARCH, when expanded, would emit a bb.error(). Referencing XEN_TARGET_ARCH in PACKAGECONFIG resulted in its expansion at the up front parse time, rather than at compile time, so non-xen-supported-archs like powerpc would see parse time errors, resulting in non-zero bitbake exit codes. Naturally this isn't ideal, so instead have the mapping function return 'INVALID' in the unsupported case, and in anonymous python, raise SkipPackage if the mapped architecture is invalid, so it's seen as unbuildable in that case. Signed-off-by: Christopher Larson <kergoth@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* xen: Add Build and Target architecture mappingNathan Rossi2015-02-201-0/+18
* Setup the XEN_TARGET_ARCH and XEN_COMPILE_ARCH based on the running environments TARGET_ARCH and BUILD_ARCH Signed-off-by: Nathan Rossi <nathan.rossi@xilinx.com>