diff options
| author | AshishKumar Mishra <emailaddress.ashish@gmail.com> | 2025-09-18 20:12:21 +0530 |
|---|---|---|
| committer | Anuj Mittal <anuj.mittal@intel.com> | 2025-09-23 10:08:04 +0800 |
| commit | 385b1baa2b2aa5d65d0db5852b3dbefa94f57abf (patch) | |
| tree | e82b45223ae6490a9f8b43814b341afea413e08b /meta-python/recipes-devtools/python/python-m2crypto/cross-compile-platform.patch | |
| parent | 5856e22d34c7b9e07e2c0038d540616bf653aa9c (diff) | |
| download | meta-openembedded-385b1baa2b2aa5d65d0db5852b3dbefa94f57abf.tar.gz | |
meta-oe: image: optionally remove RAW image after sparse image creation
When creating sparse images, the RAW image is no longer needed in
some workflows such as Android and CI pipelines. These RAW images
can be multi-GB artifacts and consume significant disk space.
This change introduces a configuration option
`DELETE_RAWIMAGE_AFTER_SPARSE_CMD` which, when set to "1",
removes the RAW image after sparse image generation.
This reduces disk usage in builds where sparse images are the
final deliverables and RAW images are not required.
Default behavior is unchanged: RAW images are kept unless the
variable is explicitly enabled:
DELETE_RAWIMAGE_AFTER_SPARSE_CMD = "1" # Delete RAW image
DELETE_RAWIMAGE_AFTER_SPARSE_CMD = "0" # Default behavior
(cherry-picked from f5246b7df447ac76ec04c6e5add398862d1c9ccd in master )
Signed-off-by: AshishKumar Mishra <emailaddress.ashish@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Diffstat (limited to 'meta-python/recipes-devtools/python/python-m2crypto/cross-compile-platform.patch')
0 files changed, 0 insertions, 0 deletions