diff options
author | Mike Crowe <mac@mcrowe.com> | 2018-05-09 12:02:35 +0100 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2018-05-11 07:49:38 +0100 |
commit | 5479654eeaaa0f81bfff54ca49369c87f1658705 (patch) | |
tree | 598349192ee37b02fbe2af5404c553d0f304ce5f /documentation/kernel-dev/kernel-dev-eclipse-customization.xsl | |
parent | 5e8ba36be5d06274cb3e04290cd5c452ba49a941 (diff) | |
download | poky-5479654eeaaa0f81bfff54ca49369c87f1658705.tar.gz |
rm_work: Stop appending _setscene to do_image_complete_setscene stamps
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 <mac@mcrowe.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/kernel-dev/kernel-dev-eclipse-customization.xsl')
0 files changed, 0 insertions, 0 deletions