diff options
| author | Leon Woestenberg <leon@sidebranch.com> | 2018-09-10 23:56:43 +0200 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2018-09-12 08:17:27 +0100 |
| commit | 65cded55fa96b1ba72149a31689c081ac27af7f7 (patch) | |
| tree | ee1bc3a7d9109f91725848fc5fc1e1be97564e81 /scripts/lib/devtool/runqemu.py | |
| parent | 678fe8c66b19f141f6869859cf365aec037e89d9 (diff) | |
| download | openembedded-core-65cded55fa96b1ba72149a31689c081ac27af7f7.tar.gz openembedded-core-65cded55fa96b1ba72149a31689c081ac27af7f7.tar.bz2 openembedded-core-65cded55fa96b1ba72149a31689c081ac27af7f7.zip | |
kernel.bbclass: do not deploy fitImage; kernel-fitimage.bbclass does that.
kernel-fitimage.bbclass replaces an occurance of "fitImage" in
KERNEL_IMAGETYPE_FOR_MAKE by an image type that is buildable for the
architecture (such as zImage). The kernel-fitimage.bbclass packs that
image as sub-image in a flattened image tree image (fitImage) and
deploys this fitImage along with the image tree source file (.its).
kernel-fitimage.bbclass does not alter KERNEL_IMAGETYPES, which thus
also contains "fitImage", which kernel.bbclass will also deploy
redundantly with different naming.
The result is a dual deployment with slightly different naming,
each with a set of symlinks.
The solution chosen is to have fitImage deployment be handled by
kernel-fitimage.bbclass, and have kernel.bbclass ignore fitImage
types during deployment.
Signed-off-by: Leon Woestenberg <leon@sidebranch.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/lib/devtool/runqemu.py')
0 files changed, 0 insertions, 0 deletions