diff options
| author | Patrick Ohly <patrick.ohly@intel.com> | 2017-01-13 15:52:31 +0100 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2017-01-19 22:45:42 +0000 |
| commit | 1f2a3cdadac1560b0e03a7be25f452ad48c27ddb (patch) | |
| tree | cf4134c6f5d4a09b5c9bbda700f01b30b70c34df /meta/recipes-devtools/gnu-config | |
| parent | 10c136a382006c0ec2679a70f47ff2446c10372c (diff) | |
| download | openembedded-core-1f2a3cdadac1560b0e03a7be25f452ad48c27ddb.tar.gz openembedded-core-1f2a3cdadac1560b0e03a7be25f452ad48c27ddb.tar.bz2 openembedded-core-1f2a3cdadac1560b0e03a7be25f452ad48c27ddb.zip | |
gcc-source.inc: cleanly disable do_rm_work
Using "deltask" assumes that do_rm_work has been added already, which
won't be the case anymore in the upcoming improved rm_work.bbclass,
because then an anonymous python method will add do_rm_work.
Setting RM_WORK_EXCLUDE works with the current and upcoming
rm_work.bbclass and is the API that is meant to be used for excluding
recipes from cleaning, so use that.
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'meta/recipes-devtools/gnu-config')
0 files changed, 0 insertions, 0 deletions