Skip to content

0.12.0: openkal 0.26 - #22

Open
Sunrisepeak wants to merge 1 commit into
mainfrom
openkal-0.26.0
Open

Sunrisepeak wants to merge 1 commit into
mainfrom
openkal-0.26.0

Conversation

@Sunrisepeak

@Sunrisepeak Sunrisepeak commented Nov 19, 2026 •

Copy link
Copy Markdown
Member

openkal 0.26.0 (mcpplibs/openkal#69) advances the specification's minor version, so every implementation releases a version that declares it. This is openkal-uefi's.

What changes

  • mcpp.toml: version 0.12.0, openkal = "^0.26.0".
  • examples/hello/mcpp.toml, examples/std/mcpp.toml: openkal = "^0.26.0".
  • examples/board/mcpp.toml: the kernel-abi layer is openkal-uefi@0.12.0, as 0.11.0 moved it.
  • README.md: one paragraph stating that nothing but the specification's version changes.

No code changes, and why

Both requirements of 0.26 are of openkal.process (clause 7.6, a start bounded by the environment alone; clause 7.18, a unit claimed only where a reference can be made), and this implementation does not provide that interface: kal_process_spawn and kal_process_job_create are not defined. The receiving side of clause 7.6 was read: src/start.cpp keeps the arguments in pool memory of their measured size (from_shell, from_load_options) and src/env.cpp indexes that vector; there is no table of a fixed number of arguments. The firmware gives a program no variables.

What was run

Nothing was built or booted locally. In this pull request's CI, with the specification at openkal-0.26.0: examples/hello builds as an EFI application, boots under OVMF and returns its status, and receives the Shell's arguments and uses its volume; it cross-builds from macOS and Windows.

Expected to wait (the platform release)

The last step of "boots under OVMF as BOOTX64.EFI" builds examples/std through openkal-platform@0.28.0, whose group names openkal-musl 0.29.6:

error: 'mcpplibs.openkal' is pinned to .../.spec (version 0.26.0) by 'std', and 'mcpplibs.openkal-musl@0.29.6' requires ^0.25.0.

It holds once the platform is released for openkal 0.26. The platform pin in examples/std/mcpp.toml, in README.md and in the workflow moves with that release and is not changed here. openkal-musl admits openkal-uefi as >=0.10.0, <0.12.0, which that release also has to widen for 0.12.0.

- openkal ^0.26.0, in the manifest and in the examples; the example's board
  names openkal-uefi 0.12.0
- no code changes: what 0.26 requires is of openkal.process, which this
  implementation does not provide, and the arguments a program receives are
  already kept at their measured size (clause 7.6)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant