- a player build ships beside the dev one — dev chords and probe surfaces go dark, and a gate enforces what a player can still reach, by medium not by module - the binary carries its own shaders and its shipped UI, finds the WoW folder by itself, and keeps its local state in one benilla-config folder - the glue screens get a capture shutter, and the engine stops depending on the protocol crate Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
33 lines
1.2 KiB
TOML
33 lines
1.2 KiB
TOML
[package]
|
|
name = "benilla-formats"
|
|
version.workspace = true
|
|
edition.workspace = true
|
|
license.workspace = true
|
|
description = "WoW 1.12.1 asset-format adapters (MPQ/BLP/DBC/ADT/WDT) and the benilla-extract CLI"
|
|
|
|
[features]
|
|
# The dev/player seam (0026, built by 1173/1174). Default-on, so every normal build keeps the
|
|
# instruments; `--no-default-features` is the player build. Here it gates exactly one thing:
|
|
# `install::candidates`' project-folder probe, which bakes THIS source tree's absolute path
|
|
# (decision 1175). EVERY dependent must take this crate with `default-features = false` and
|
|
# re-export `dev`, or feature unification puts `/Users/…` back into a player binary —
|
|
# `scripts/gates.sh`'s `--no-default-features` line is what catches getting that wrong.
|
|
default = ["dev"]
|
|
dev = []
|
|
|
|
[dependencies]
|
|
anyhow.workspace = true
|
|
clap.workspace = true
|
|
benilla-adt = { path = "../benilla-adt" }
|
|
benilla-bytes = { path = "../benilla-bytes" }
|
|
benilla-dbc = { path = "../benilla-dbc" }
|
|
benilla-m2 = { path = "../benilla-m2" }
|
|
benilla-mpq = { path = "../benilla-mpq" }
|
|
benilla-blp = { path = "../benilla-blp" }
|
|
image = "0.25"
|
|
benilla-wdt = { path = "../benilla-wdt" }
|
|
benilla-wmo = { path = "../benilla-wmo" }
|
|
|
|
[dev-dependencies]
|
|
glam = "0.31"
|