updated cargo.toml, and contributing.md

This commit is contained in:
ademerdogan2008 2026-06-26 12:36:41 -05:00
parent 6dd3c610f0
commit 83ab5d8ec7
2 changed files with 6 additions and 3 deletions

View file

@ -95,12 +95,14 @@ cargo run --release --features profile-with-tracy -- serve
3. In Tracy, connect to the running `rojo` process. 3. In Tracy, connect to the running `rojo` process.
4. Perform the actions you want to profile (syncing, building, etc.) and inspect the timeline in Tracy. 4. Perform the actions you want to profile (syncing, building, etc.) and inspect the timeline in Tracy.
Short-lived commands like `build` may exit before Tracy can connect. Set `TRACY_NO_EXIT=1` to keep the process alive until you connect: Short-lived commands like `build` may exit before Tracy can connect. Set `TRACY_NO_EXIT=1` to keep the process alive until you connect (not supported on macOS):
```bash ```bash
TRACY_NO_EXIT=1 cargo run --release --features profile-with-tracy -- build TRACY_NO_EXIT=1 cargo run --release --features profile-with-tracy -- build test-projects/benchmark_small_place --output /tmp/out.rbxlx
``` ```
On macOS, prefer profiling long-running commands like `serve` instead.
### Adding instrumentation ### Adding instrumentation
Use these `profiling` macros in Rust code: Use these `profiling` macros in Rust code:

View file

@ -31,7 +31,8 @@ default = []
dev_live_assets = [] dev_live_assets = []
# Run Rojo with this feature to open a Tracy session. # Run Rojo with this feature to open a Tracy session.
# Currently uses protocol v63, last supported in Tracy 0.9.1. # See CONTRIBUTING.md for setup instructions. Match the Tracy GUI version to
# the tracy-client-sys version in Cargo.lock (see the tracy-client version table).
profile-with-tracy = ["profiling/profile-with-tracy"] profile-with-tracy = ["profiling/profile-with-tracy"]
[workspace] [workspace]