Add production build pipeline
CI / build-and-test (pull_request) Successful in 1m30s
CI / production-build (pull_request) Successful in 19m17s

This commit is contained in:
2026-09-19 18:35:32 +02:00
parent 804e5e37e0
commit e10f0848bc
8 changed files with 152 additions and 12 deletions
+18
View File
@@ -13,3 +13,21 @@ cargo run -- --debug-match --players 2 --local-port 7000 \
cargo run -- --debug-match --players 2 --local-port 7001 \
--net-player 0=127.0.0.1:7000 --net-player 1=local
```
## Production Build
Production builds use the `production` Cargo profile and do not dynamically
link Bevy or Rust. Development builds retain Bevy dynamic linking for faster
iteration. Cargo stores the production profile under `target/production`,
separate from development artifacts under `target/debug`.
```sh
cargo run --locked \
--bin process-assets --no-default-features --features debug_features
cargo build --locked \
--profile production --no-default-features --features debug_features
```
The asset preprocessing command must be run from the repository root. It
populates `imported_assets/Default`, which is then consumed by the production
game without running the asset processor at startup.