There's already a variable for "the host python to use during the build
when cross-compiling", so there's no need to add another.
(From OE-Core rev: 1ede9777478469fbdb633782e0ffb2ae68b1a578)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Use EXTRA_OECONF and CACHED_CONFIGUREVARS as nature intended.
(From OE-Core rev: 260804462766116941a1d9100ef8be3e66b93300)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The manifest parsing code was only adding .py and .pyc paths to FILES,
generalise the latter to .py? so it catches .pyo files too.
(From OE-Core rev: 1e0ef76dcccfa10cdf473670acd2c52332bb3412)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Instead of passing the same five variables to oe_runmake repeatedly, add them to
EXTRA_OEMAKE once.
(From OE-Core rev: c4ae09134732e4e95f17d6e572756bec49a9e3d0)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
There's no need to patch in HOSTPGEN when we can just override PGEN directly.
(From OE-Core rev: d274a3d3bd90d8726752c3a18bc15fdf6bc2f37d)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Drop backports, rebase a couple of patches.
This is the second last release of py 2.x; upstream support ends on
1 January 2020, there will be one final 2.x afterwards.
Note that the only thing that still needs python 2.x in oe-core is
u-boot; when the next u-boot update arrives, we should find out
where the py3 migration is for that component before merging the
update.
(From OE-Core rev: 184b60eb905bb75ecc7a0c29a175e624d8555fac)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
