You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ba5865e
Browse filesBrowse the repository at this point in the historyBrowse files
0.6.3: a core runner for an implementation without files, processes or threads
One interface (include/okrun.h, run/src/runner.h, the bindings) has two
runners, selected in run/mcpp.toml by the interfaces the implementation
provides (cfg(interface = ...), mcpp 2026.11.13.1). With openkal.fs,
openkal.process, openkal.task, openkal.random and openkal.map it is the full
runner (run/src/full), unchanged. Without any of them it is the core runner
(run/src/core), which runs what the program carries from memory --- an image,
a group, or an archive --- with the same admission and loader, and without
cache, snapshot or profiler; okrun_run_file refuses with the reason. A callback
of an absent interface is absent, as its other names are. openkal-run requires
only abort, env, exec, memory, stream and time.
Copy file name to clipboardExpand all lines: ld/mcpp.toml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
[package]
2
2
namespace = "mcpplibs"
3
3
name = "openkal-ld"
4
-
version = "0.6.2"
4
+
version = "0.6.3"
5
5
description = "libokld: the ok format (openkal image format) --- its definition, a reader of bytes, a checker, a signer, and a loader. Freestanding: no C library, no exceptions."
description = "libokrun: the runner's core --- an ok image's names bound to this process's one openkal implementation, in the image's calling convention, and its entry entered."
0 commit comments