shoney.arickathil
5d780d8669
- a directory carrying wo.toml is a PROJECT: `woc .` inside it (or `woc path/to/project` from anywhere) reads the manifest and produces <target>/<name>, exactly what `woc build <dir> -o ...` produces - schema is the one the sample already carried -- top-level name/ version/description, [runtime] wo (accepted, not yet enforced) -- plus a new [build] section: runtime (wovm to prepend) and target (output dir, default "target"), both relative to the manifest's own directory so the build is invocation-point independent - unknown keys and sections are hard errors: a typo'd key silently ignored would build the wrong thing - directories WITHOUT wo.toml keep check-only semantics -- the corpus is full of those; oop-e2e 71/0, woc-test 565/0, log-watcher 7/0 - sample's wo.toml gains the [build] section; target/ gitignored Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
17 lines
665 B
TOML
17 lines
665 B
TOML
name = "log-watcher"
|
|
version = "0.1.0"
|
|
description = "The Haxe log-watcher ported file-for-file: the systems-track sample workload (program mode + fs/proc/net/time/json)"
|
|
|
|
# A free `fn main` makes this a PROGRAM (systems-track spec Part 2): one
|
|
# shard, blocking builtins legal, exit code = main's return value. No [app]
|
|
# listen — the mcp subcommand takes its port from config.json, like the
|
|
# original.
|
|
|
|
[runtime]
|
|
wo = ">= 0.1"
|
|
|
|
# `woc .` in this directory (or `woc docs/examples/log-watcher` from the
|
|
# repo root) builds target/log-watcher from this manifest. Paths resolve
|
|
# against this file's directory.
|
|
[build]
|
|
runtime = "../../../runtime/wovm"
|