diff options
| author | Ming Liu <ming.liu@toradex.com> | 2019-09-06 15:54:59 +0800 |
|---|---|---|
| committer | Ming Liu <ming.liu@toradex.com> | 2019-09-07 16:12:56 +0800 |
| commit | f6189abd8e5ce3b2f303a5deb55ac887f5707073 (patch) | |
| tree | 153c937f570d50a1f19e07ff38ddcf70468566dd | |
| parent | a167caa4eabd8a54e2d4f4f9638f4a12cd4fb52f (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>
| -rw-r--r-- | classes/image_type_tezi.bbclass | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/classes/image_type_tezi.bbclass b/classes/image_type_tezi.bbclass index 258e4d7..4456cd3 100644 --- a/classes/image_type_tezi.bbclass +++ b/classes/image_type_tezi.bbclass @@ -14,6 +14,8 @@ do_image_teziimg_distro[recrdeptask] += "do_deploy" WKS_FILE_DEPENDS_append = " tezi-metadata" DEPENDS += "${WKS_FILE_DEPENDS}" +RM_WORK_EXCLUDE += "${PN}" + TEZI_ROOT_FSTYPE ??= "ext4" TEZI_ROOT_LABEL ??= "RFS" TEZI_ROOT_SUFFIX ??= "tar.xz" |