Skip to content

openkal 0.16.0, and the seven packages that move with it - #565

Merged
Sunrisepeak merged 2 commits into
mainfrom
openkal-0.16.0
Oct 24, 2026
Merged

Sunrisepeak merged 2 commits into
mainfrom
openkal-0.16.0

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

The rows for openkal 0.16.0, openkal-linux 0.17.0, openkal-macos 0.14.0, openkal-windows 0.12.0, openkal-emscripten 0.5.0, openkal-opensbi 0.8.3, openkal-musl 0.21.0 and openkal-llvm-runtime 0.15.5, in all three platform tables.

Every GLOBAL address is the upstream tag archive and every CN address is the byte-identical gitcode asset in mcpp-res; each pair was downloaded and compared against the recorded sha256. mcpp xpkg parse --all-os reports parse OK for all eight descriptors.

The specification adds kal_task_start_sized (a least stack size) and KAL_TERM_PASS_INPUT (whether input is altered), and states what closing a directory does to its enumerations (mcpplibs/openkal#50).

The specification adds kal_task_start_sized and KAL_TERM_PASS_INPUT and states
what closing a directory does to its enumerations. Every GLOBAL address is the
upstream tag archive and every CN address is the byte-identical gitcode asset,
checked against the recorded sha256 for each.
…builds it on, and openkal has consumers

mcpp locks what the host resolves, so a lockfile proves a platform package only
on that platform's runner. member_platforms reads the consumer's manifest: an
unconditional dependency is scheduled on all three runners, one under cfg(os = ...)
or cfg(windows) on that runner, and one under any other condition on none, its
own repository measuring it on its target. test_ci.py covers the rule.

tests/examples/openkal names the specification everywhere and each
implementation for its own system, and observes the newest declarations;
tests/examples/openkal-musl runs the programs three reports were written with.
@Sunrisepeak
Sunrisepeak merged commit 0292416 into main Oct 24, 2026
29 checks passed
@Sunrisepeak
Sunrisepeak deleted the openkal-0.16.0 branch October 24, 2026 22:56
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