diff options
author | Ming Liu <ming.liu@toradex.com> | 2019-09-06 15:54:59 +0800 |
---|---|---|
committer | Peter Liu <peter.liu@se.atlascopco.com> | 2019-09-12 11:50:01 +0800 |
commit | 76a2d63ef49cea30324c7d93913ebc9d24bac406 (patch) | |
tree | 5594a977ebd90109b23d5fb8de03ff1198b4ae7a /recipes-bsp/u-boot/u-boot-distro-boot/sota/boot.cmd.in | |
parent | a93a01d59fc88d28c97ee0eb354a9747463b79df (diff) |
image_type_tezi.bbclass: set RM_WORK_EXCLUDE
The image recipes do not really support rm_work, I have observed a lot
of build issues when I modified some do_image tasks while do_rootfs not
touched, to give a example:
The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function: <module>
0001:
*** 0002:buildinfo(d)
0003:
File: 'meta/classes/image-buildinfo.bbclass', lineno: 67, function: buildinfo
0063:# Write build information to target filesystem
0064:python buildinfo () {
0065: if not d.getVar('IMAGE_BUILDINFO_FILE'):
0066: return
*** 0067: with open(d.expand('${IMAGE_ROOTFS}${IMAGE_BUILDINFO_FILE}'), 'w') as build:
0068: build.writelines((
0069: '''-----------------------
0070:Build Configuration: |
0071:-----------------------
so we set RM_WORK_EXCLUDE to avoid running into those problems.
Signed-off-by: Ming Liu <ming.liu@toradex.com>
Diffstat (limited to 'recipes-bsp/u-boot/u-boot-distro-boot/sota/boot.cmd.in')
0 files changed, 0 insertions, 0 deletions