scripts/image: build an image for each UBOOT_SYSTEM #3470
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes it possible to build multiple images based on the same
.kernel
and.system
files.When is multiple images built?
Building of multiple images is only activated when
BOOTLOADER
isu-boot
,UBOOT_SYSTEM
is empty,DEVICE
is set and boards is defined inscripts/uboot_helper
.How is images built?
The
u-boot
package is built with emptyUBOOT_SYSTEM
and onlyupdate.sh
,canupdate.sh
and dtbs is installed into.system
file at/usr/share/bootloader
.The device universal update
<IMAGE_NAME>.tar
file is createdFor each uboot system returned by
scripts/uboot_helper <PROJECT> <DEVICE>
:u-boot
package is re-built and re-installed withUBOOT_SYSTEM
setbootloader/release
is invoked to copy theu-boot
files to3rdparty/bootloader
scripts/mkimage
is invoked and will generate a<IMAGE_NAME>-<UBOOT_SYSTEM>.img.gz
imageHow does images differ?
The images produced will differ slightly from an image built with
UBOOT_SYSTEM
set:u-boot
files installed bybootloader/install
is not added to the final imageu-boot
Example
Running
PROJECT=Rockchip ARCH=arm DEVICE=RK3328 make image
will produce: