enricobuehler
0d8b156dcc
ci / bun-nix (pull_request) Successful in 25s
ci / docs-drift (pull_request) Successful in 30s
ci / web (pull_request) Successful in 1m49s
ci / docs-site (pull_request) Successful in 1m54s
apple / swift (pull_request) Successful in 2m7s
apple / distribute (pull_request) Skipped
apple / screenshots (pull_request) Skipped
ci / rust-arm64 (pull_request) Successful in 5m41s
android / android (pull_request) Successful in 6m37s
windows-client / client (x64, , x86_64-pc-windows-msvc, C:\t) (pull_request) Successful in 9m0s
nix / flake (pull_request) Successful in 8m38s
windows-client / client (arm64, --no-default-features, aarch64-pc-windows-msvc, C:\t-a64) (pull_request) Successful in 4m22s
ci / rust (pull_request) Successful in 19m45s
The ring layer moves out of the session binary into pf_client_core::logring (desktop-gated beside the ring it feeds) — it started as punktfunk-session's private module, and the moment both desktop shells wanted the row, a copy per bin was exactly the drift the crate exists to prevent. The session keeps the same layer under its new name; tracing-log and log fall out of its manifest. Both shells install it beside their visible layer with its own DEBUG filter — the env filter keeps scoping only what's printed, because the ring exists for the diagnostics nobody enabled before the bug happened. The row itself lands on each shell's saved-host menu on the console's own gate (paired + online), wired to logring::send_to_host on a worker thread, outcome as a toast (GTK) / the status line (WinUI), in the console's wording verbatim. And the bundle is worth sending: orchestrate now pipes the session child's stderr through logring::forward_child_stderr — every line still lands on our stderr exactly as inherit interleaved it, and lands in the ring too. Without that, the one surface a GUI-only user can export held everything EXCEPT the stream it was exported about — the same hole the WinUI logfile module was built to close for the file; its child forwarder now feeds the ring on the same pass.
56 lines
2.9 KiB
TOML
56 lines
2.9 KiB
TOML
[package]
|
|
name = "punktfunk-client-session"
|
|
description = "punktfunk/1 Vulkan session binary — SDL3 window, ash presenter, terminal stats; the power-user / gamescope stream client"
|
|
version.workspace = true
|
|
edition.workspace = true
|
|
rust-version.workspace = true
|
|
license.workspace = true
|
|
authors.workspace = true
|
|
repository.workspace = true
|
|
|
|
[[bin]]
|
|
name = "punktfunk-session"
|
|
path = "src/main.rs"
|
|
|
|
[features]
|
|
default = ["ui", "pyrowave"]
|
|
# PyroWave client decode (the wired-LAN wavelet codec) — enables the decode backend + the
|
|
# planar present path. ON by default; each session still opts in explicitly (the Settings
|
|
# codec pick, or PUNKTFUNK_PREFER_PYROWAVE=1). The Windows ARM64 leg builds
|
|
# --no-default-features and so skips it — note that also drops `ui` (the Skia console/OSD),
|
|
# not just pyrowave; hardware video decode itself (D3D11VA / Vulkan Video) is unaffected.
|
|
pyrowave = ["pf-client-core/pyrowave", "pf-presenter/pyrowave"]
|
|
# The Skia console UI (stats OSD, capture HUD, later the gamepad library). Dropping it
|
|
# (`--no-default-features`) is the ~15 MB-smaller power-user build: same streaming,
|
|
# stats on stdout only.
|
|
ui = ["dep:pf-console-ui", "dep:serde_json"]
|
|
# Same Linux+Windows gating as the rest of the client stack; elsewhere this is a stub
|
|
# binary.
|
|
[target.'cfg(any(target_os = "linux", windows))'.dependencies]
|
|
# `default-features = false` on both: THIS crate's `pyrowave` feature (above) is the single
|
|
# switch that turns the wavelet codec on, and it enables it explicitly on each. Inheriting their
|
|
# defaults instead would make `--no-default-features` a lie — the Windows ARM64 leg builds that
|
|
# way precisely to skip the vendored PyroWave C++, which has no ARM64 SIMD path.
|
|
pf-presenter = { path = "../../crates/pf-presenter", default-features = false }
|
|
pf-console-ui = { path = "../../crates/pf-console-ui", optional = true }
|
|
pf-client-core = { path = "../../crates/pf-client-core", default-features = false }
|
|
punktfunk-core = { path = "../../crates/punktfunk-core", features = ["quic"] }
|
|
# The fake-library dev hook (`PUNKTFUNK_FAKE_LIBRARY`, browse mode) parses GameEntry JSON.
|
|
serde_json = { version = "1", optional = true }
|
|
tracing = "0.1"
|
|
tracing-subscriber = { version = "0.3", features = ["env-filter"] }
|
|
|
|
# This crate carries NO toolkit, deliberately: it is the renderer the shells spawn, and the
|
|
# `--no-default-features` build is what a minimal/embedded image installs. GTK4/libadwaita/relm4
|
|
# belong to `clients/linux` (the shell) and must never appear here — a stray copy of the shell's
|
|
# modules landed in src/ once (b0ea1e6b) and dragging its dependencies in behind it is what let
|
|
# the wrong `main.rs` build and ship as `punktfunk-session`.
|
|
|
|
# Embeds the app icon as an exe resource (build.rs) — Windows hosts only (rc.exe from
|
|
# the SDK); same pattern as clients/windows.
|
|
[target.'cfg(windows)'.build-dependencies]
|
|
winresource = "0.1"
|
|
|
|
[lints]
|
|
workspace = true
|