linux/poky.git/meta/classes/rm_work.bbclass, branch warrior

rm_work: sort the value of do_build dependencies

2019-03-09T14:43:11+00:00

This fixes some 'basehash changed' errors when rm_work is being inherited. (From OE-Core rev: e74158b6cc1d683ab14ef5d47ec531f986fc2259) Signed-off-by: Ming Liu Signed-off-by: Richard Purdie

rm_work: Simplify looping code

2018-06-21T08:34:40+00:00

The current looping structure is confusing, simplify it a bit to improve readability. Should be no functionality changes. (From OE-Core rev: 498065b51b205b43d7dae1008014eba85a8f138c) Signed-off-by: Richard Purdie

rm_work: Improve code comments

2018-06-21T08:34:40+00:00

This function is a little obtuse, add more comments about what its doing and why. Also combine some of the statements where possible to improve clarity. (From OE-Core rev: 3e0c22e9bd9757cd458a073a3f043a48184d7bab) Signed-off-by: Richard Purdie

rm_work: The do_setscene task has not existed for years

2018-06-21T08:34:40+00:00

Once, there were do_setscene tasks but this hasn't been the case for years, drop the old code. (From OE-Core rev: b13a691f1cfc0d68a0f94c343fa3a1b987dbe117) Signed-off-by: Richard Purdie

rm_work: Stop appending _setscene to do_image_complete_setscene stamps

2018-06-21T08:34:40+00:00

This is a reworked version of the issue which 5479654eeaaa0f81bfff54ca49369c87f1658705 attempted to fix. """ Each time I build my image after the first, I end up with a do_image_complete_setscene stamp file with an extra _setscene appended to the name. Eventually, the filenames end up being so long that mv complains and the build fails. It looks like this behaviour was introduced when the special handling was added for do_image_complete in 2ff9d40dc88d43567472218cf3d3faf414398c71. """ Instead of the original approach which broke do_package_setscene, add an entry to explictly stop the stacking _setscene pieces on do_image_complete. It's not straightforward to just move *do_image_complete* after the *_setscene* pattern because do_image_complete stamps would then match do_image*. (From OE-Core rev: 0f4e734e0ef40076351ed7ff795aac36197e4949) Signed-off-by: Richard Purdie

Revert "rm_work: Stop appending _setscene to do_image_complete_setscene stamps"

2018-06-21T08:34:40+00:00

Whilst this fixes the do_image_complete_setscene append problem, it creates a new problem since the code can no longer reach the *do_package_setscene.* code block below it. This breaks builds as per [YOCTO #12765]. Revert this change in search of a better fix. This reverts commit 5479654eeaaa0f81bfff54ca49369c87f1658705. Signed-off-by: Richard Purdie

rm_work: Stop appending _setscene to do_image_complete_setscene stamps

2018-05-11T06:49:38+00:00

Each time I build my image after the first, I end up with a do_image_complete_setscene stamp file with an extra _setscene appended to the name. Eventually, the filenames end up being so long that mv complains and the build fails. It looks like this behaviour was introduced when the special handling was added for do_image_complete in 2ff9d40dc88d43567472218cf3d3faf414398c71. So, let's ensure that the *_setscene* pattern is matched before anything else so that any do_image_complete_setscene stamp file is always ignored and the do_image_complete non-setscene stamp file is moved only once. It's not straightforward to just move *do_image_complete* after the *_setscene* pattern because do_image_complete stamps would then match do_image*. (From OE-Core rev: f04e6bd144deb0c8fe2742f66b18904b6619a502) Signed-off-by: Mike Crowe Signed-off-by: Richard Purdie

rm_work: remove debugging statements

2018-01-02T17:24:38+00:00

(From OE-Core rev: e7da9a3adc1ed430fff7afae4233e62313759b65) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

rm_work: Handle race with -inital tasks

2017-12-21T10:21:00+00:00

There is a race with rm_work when tasks run deltask do_build since do_rm_work becomes a floating task. Handle this by injecting the populate_sysroot/lic dependencies manually if the tasks returned are empty. This depends on a change to fix bb.build.preceedtask() in bitbake too. [YOCTO #12365] (From OE-Core rev: 0f537d985b7b17af508a511fca8a4ec4b5804580) Signed-off-by: Richard Purdie

rm_work: fix build break for do_image_complete

2017-08-15T23:03:14+00:00

* since following commit: commit 2ff9d40dc88d43567472218cf3d3faf414398c71 Author: Richard Purdie Date: Sun Jul 30 16:06:57 2017 +0100 image/rm_work: Promote do_image_complete to be more sstate like all image rm_work tasks are failing with: mv: 1.0-r0.do_image_complete.228730130ba309f85b73b72222ba11d7.raspberrypi3 and 1.0-r0.do_image_complete.228730130ba309f85b73b72222ba11d7.raspberrypi3 are the same file it's because for $i 1.0-r0.do_image_complete.228730130ba309f85b73b72222ba11d7.raspberrypi3 there will be first SSTATETASK in $j do_deploy, so the sed call doesn't replace anything It might be different order of SSTATETASKS in my builds (it might work only when do_image_complete is the first one in the list), but here: SSTATETASKS="do_deploy do_image_complete do_image_qa do_package do_package_qa do_package_write_ipk do_packagedata do_populate_lic do_populate_sdk do_populate_sdk_ext do_populate_sysroot" (From OE-Core rev: 0c905d4e7fa8e5416945fa0d61ebc1d34409d1e6) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie