Move to a post post-image world #1267
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wkz
force-pushed
the
post-post-image
branch
10 times, most recently
from
bf65879 to
8d8f587
Compare
A bunch of different artifacts should follow the same naming scheme, depending on a bunch of config settings + whether we're building a release or not. Therefore, provide a single definition of this that we can reuse to name disk images, upgrade packages, etc.
The board/*/*/*.mk is very broad, intended to hit all board specific definitions, but may also cause duplicate inclusions, e.g., in board/common. Let each architecture do the inclusion instead.
Rather than using the creation of a signed image as a proxy for whether the trusted keys should be installed RAUC/U-Boot's trust stores, use the dedicated option.
Add scaffolding for breaking out image generation to separate make targets.
Add a generic image target to build aux.ext4, which can be used both when creating target-specific SD-card images, and when creating regular disk images. While we're here, make sure that we don't need a RAUC bundle in order to generate aux.ext4 (which mkrauc-status.sh did). This saves us time on _every_ incremental build.
We have not installed .dtb:s to $O/images/ for quite some time, and nobody cared. That goes to show that this is not really used. The image is still useful at times, so if it needed in the future, then we can resurrect it from the logs and refactor it to an image package.
Limit support to x86, like we do on the "official" appliances on the marketplace. Aarch64 has never really been used AFAIK. Avoid the os-release import, since all that info is not important now that these appliance files are only for development scenarios. In all other cases, the official one, based on a proper release, should be used.
This is an internal artifact, so there is no need to give it a branded name.
Remnants from the olde country.
Now that all components are generated from their own fragments, we have no need for post-image.sh anymore.
Previously, post-image.sh was able to create QEMU images from an existing release tarball. This was useful when you wanted to test a new bootloader build without having to wait for a full Infix build. Restore this capability by adding a separate image target for it, and then allow image-itb-qcow to source its input images from that instead of a locally build squash+aux.
This CPU has less emulation overhead than `max`, which is what we mostly care about.
Use the new image-itb-dl-release to compose a QCOW with Infix and U-Boot, in the same way that we previously did in post-image.sh.
troglobit
approved these changes
Dec 3, 2025
Contributor
troglobit
left a comment
troglobit
left a comment
There was a problem hiding this comment.
Much needed cleanup, nice work!
Contributor
Author
|
One failing test on Not sure what happened there (or why the report was not uploaded). But seems more likely to be some flaky thing in the test (given that it was added very recently), or what do you think @troglobit? |
Contributor
Agreed, very likely flaky new test. Created #1303 for this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Checklist
Tick relevant boxes, this PR is-a or has-a: