Skip to content

0.19.3 --- the implementations of openkal 0.14.1 beneath #45

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Sunrisepeak merged 1 commit into from
Oct 1, 2026
Merged

0.19.3 --- the implementations of openkal 0.14.1 beneath #45

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ the claim can be checked rather than repeated.

```toml
[dependencies]
openkal-musl = "0.16.0"
openkal-musl = "0.19.3"
```

> **Engine floor (mcpp 2026.9.18.3):** this version of this package declares
Expand Down
12 changes: 6 additions & 6 deletions mcpp.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
[package]
namespace = "mcpplibs"
name = "openkal-musl"
version = "0.19.2"
version = "0.19.3"
description = "musl 1.2.5 redirected onto openkal: one C library, ported once, above every implementation of the specification rather than above one kernel."
license = "Apache-2.0"

Expand Down Expand Up @@ -146,7 +146,7 @@ lchown = { form = "enosys", note = "as chown" }
tcsetattr = { form = "accepted-no-effect", note = "openkal names three positions of the terminal mode word; a request that alters output post-processing, the line speed, the control characters or VMIN/VTIME is accepted and that part has no effect" }

[dependencies]
openkal = "0.14.0"
openkal = "0.14.1"

# An ordinary consumer of openkal declares the specification and leaves the
# choice of implementation to whoever builds the program, which is what the
Expand All @@ -161,7 +161,7 @@ openkal = "0.14.0"
#
# The consequence for a program is that it names this package and nothing else.
[target.'cfg(os = "linux")'.dependencies]
openkal-linux = { version = "0.15.0", features = ["standalone"] }
openkal-linux = { version = "0.15.1", features = ["standalone"] }

[target.'cfg(os = "macos")'.dependencies]
# 0.12.0 is the first release of this implementation that declares which
Expand All @@ -171,7 +171,7 @@ openkal-linux = { version = "0.15.0", features = ["standalone"] }
# is the shape of a check that silently does not run --- while the same
# consumer was answered on Linux and Windows, whose implementations have
# carried the array since openkal-linux 0.15.0 and openkal-windows 0.10.0.
openkal-macos = { version = "0.12.0", features = ["standalone"] }
openkal-macos = { version = "0.12.1", features = ["standalone"] }

# FIRST STEP TOWARD A BARE MACHINE, AND NOT THE WHOLE OF IT.
#
Expand All @@ -182,7 +182,7 @@ openkal-macos = { version = "0.12.0", features = ["standalone"] }
# runtime that receives control, and a C library configured for an environment
# with no process to exit from. So this declares the implementation and stops.
[target.'cfg(os = "none")'.dependencies]
openkal-opensbi = { version = "0.8.0", features = ["standalone"] }
openkal-opensbi = { version = "0.8.1", features = ["standalone"] }

# WHICH OPENKAL INTERFACES THE IMPLEMENTATION BENEATH IS EXPECTED TO PROVIDE.
#
Expand All @@ -207,7 +207,7 @@ openkal-opensbi = { version = "0.8.0", features = ["standalone"] }
defines = ["OKM_HAS_FS=0", "OKM_HAS_PROCESS=0", "OKM_HAS_TASK=0"]

[target.'cfg(windows)'.dependencies]
openkal-windows = { version = "0.10.1", features = ["standalone"] }
openkal-windows = { version = "0.10.2", features = ["standalone"] }

# The feature macros musl's own build establishes.
#
Expand Down
Loading