Add AArch64 container variants #65
Conversation
|
I suggest something like |
Sounds good. Have rebased the branch and added a line to make |
lsf37
force-pushed
the
armv8_testing
branch
14 times, most recently
from
2de3f8d
to
ff2412c
Compare
|
Before merging we should update https://github.com/seL4/seL4-CAmkES-L4v-dockerfiles?tab=readme-ov-file#to-build-the-local-dockerfiles. |
|
I can't approve my own pull requests so I'll just leave a comment saying I don't see any issues with any of the changes. |
Perfect. I'll remove the comment you mentioned above and merge when the tests pass. |
Add an AArch64 version of the seL4, CAmkES, and L4v containers. seL4 and CAmkES should have full functionality, L4v will be missing the mlton compiler. The Intel containers remain available as before. Co-authored-by: Gerwin Klein <[email protected]> Signed-off-by: Gerwin Klein <[email protected]>
Signed-off-by: Gerwin Klein <[email protected]>
- remove obsolete options and settings - spell check - update github org URLs - update descriptions to current seL4 CI - update CLI instructions - markdown lint Signed-off-by: Gerwin Klein <[email protected]>
Prevent the job from using cached images on the self-hosted runner to make sure we are picking up the current state of the remote Debian repo. GitHub runners start from scratch each time, so they won't have any cached images available. Signed-off-by: Gerwin Klein <[email protected]>
Building seL4 projects and CAmkES projects should work now. The l4v container will build, but on ARM64 will be missing the
mltoncompiler.Also includes CI setup (for PRs only for now) and README update.
Both, x64 and arm64 images should be working, but the setup is not yet a full multi-arch build where one container manifest contains both images at the same time. We can do that in a separate step.