[OE-core] [PATCH 0/2] eSDK: enhance compatibility with rm_work
Patrick Ohly
patrick.ohly at intel.com
Wed Mar 29 11:29:48 UTC 2017
Currently "-c populate_sdk_ext" enables do_rm_work and then fails when
that runs first. This is simular to the problem discussed with Mike
Crowe: additional tasks that are only meant to run when explicitly
requested by the user cannot be ordered to run before do_rm_work
without also making them part of normal builds.
IMHO this has always been a problem, injecting do_rm_work before
do_build just triggers it more often.
There's no good solution besides avoiding do_rm_work, which is what
the two following patches do. The more reliable solution would be to
have additional ordering dependencies between tasks than the current
"A must run before B".
I also considered solving this in the task scheduler, but I believe
that this wouldn't work because even if it schedules populate_sdk_ext
before rm_work, it wouldn't be able to prevent rm_work from running in
parallel to populate_sdk_ext.
Patrick Ohly (2):
rm_work.bbclass: introduce do_build_without_rm_work
populate_sdk_ext.bbclass: enhance compatibility with rm_work.bbclass
meta/classes/populate_sdk_ext.bbclass | 7 ++++++-
meta/classes/rm_work.bbclass | 27 ++++++++++++++++++++++++---
2 files changed, 30 insertions(+), 4 deletions(-)
base-commit: d68a86d87aa017dd0fecb0f626d22711efefcd3f
--
git-series 0.9.1
More information about the Openembedded-core
mailing list