build(tracy): mise run tracy-tools builds tracy-capture and tracy-csvexport 0.15.0 into _deps #1746

Merged
HumanBean merged 1 commit from HumanBean/Longshot:build/tracy-tools into main 2026-11-19 14:59:44 +00:00
Owner

Type: build · Risk: low · Tested on: CachyOS Linux (cmake 4, ninja, clang) · Needs: nothing

TL;DR

Profiling the game with Tracy needs tracy-capture (and tracy-csvexport to read a capture as text) at exactly 0.15.0, the game's client's protocol version. Tracy publishes programs for Windows only, so on Linux everyone built them by hand. mise run tracy-tools now builds both from the pinned source, SHA-256 checked, into the checkout's _deps/tracy-0.15.0/bin.

Breakdown

  • Who it helps: developers profiling the game on Linux (LONGSHOT_TRACY=1 builds, docs/development/tracy.md).
  • What was wrong: no Linux binaries of Tracy's tools exist, and a version other than 0.15.0 can't talk to the game's client.
  • What changes: a tracy-tools mise task: it downloads Tracy v0.15.0's source tarball, checks its SHA-256, builds capture and csvexport with cmake and ninja, and copies both programs to _deps/tracy-0.15.0/bin (inside the checkout, ignored as _deps/ is; nothing global). A second run sees them and stops. The Capture section of tracy.md names the task.
  • What does not change: the game, its Tracy client (third_party/tracy), any build of the game, and the other tasks.
  • How it was checked: the task run from scratch on Linux: both programs built and captured from a LONGSHOT_TRACY=1 game (a Castle Town Market capture, exported with tracy-csvexport); a second run said "already built".
  • What is still open: nothing.
  • Risk: low: a developer task, run only on request.

Why

Finding where the game's frames go, for the performance work, needed Tracy captures on Linux; the tools had to be built by hand from source, each time into a different place. A task makes that one command, into a folder of the checkout, at the one version that works.

What changed

  • mise.toml: [tasks.tracy-tools] (Linux and macOS shells; it checks for cmake, ninja and c++ first and says which is missing).
  • docs/development/tracy.md: the Capture section names the task.

Measurements

Nothing to measure: a developer task that changes no build of the game.

Flags and settings

None.

Testing

Tested: CachyOS Linux: mise run tracy-tools from an empty _deps/: the tarball's checksum checked, both tools built (_deps/tracy-0.15.0/bin/tracy-capture, tracy-csvexport); tracy-capture -a 127.0.0.1 took a capture from a LONGSHOT_TRACY=1 game and tracy-csvexport read it; a second run stopped at "already built".

Not tested: macOS (it should build the same way, untried). Windows has Tracy's own release programs; the task needs bash. mise run test: not run on this PC.

Must be tested:

  • macos, by hand: mise run tracy-tools from an empty _deps/, expecting tracy-capture and tracy-csvexport in _deps/tracy-0.15.0/bin and tracy-capture -a 127.0.0.1 connecting to a LONGSHOT_TRACY=1 game

Risks

What could break: nothing outside the task.

Turning it off: don't run it; or revert.

Compatibility: Nothing changes: no option, cache or API.

Checklist

Everyone

  • One topic.
  • The title is a Conventional Commit (type(scope): description) of the status line's type.
  • Why gives the reason plainly and links the issues that fit (the tracker searched).
  • Tested on my own PC where it runs (in the game, for a change the game runs), as Testing's Tested says; what
    can't be run by hand is in Testing's Not testable by hand, with why.
  • Measurements has a verdict, or one line saying why there is nothing to measure.
  • Nothing gets worse that I know of: any cost (speed, latency, memory, a setup that worked before) is measured and
    in Risks.
  • Testing names what was tested, what wasn't, and what must still be tested, where and how.
  • Rebased on current main.
  • python -I -B tests/run_all.py passes (any failure that also fails on main is named). Not run on this PC.
  • No game files, dumps, build output or generated files.
  • third_party/ untouched (a new folder with a PROVENANCE.md instead).
  • The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled.

When it applies

  • AI assistance recorded with Assisted-by: / Co-Authored-By: trailers.
  • Docs updated.

🤖 Generated with Claude Code

https://claude.ai/code/session_016o1k1PazAdTJxQQWQBksW2

**Type:** build · **Risk:** low · **Tested on:** CachyOS Linux (cmake 4, ninja, clang) · **Needs:** nothing ## TL;DR Profiling the game with Tracy needs `tracy-capture` (and `tracy-csvexport` to read a capture as text) at exactly 0.15.0, the game's client's protocol version. Tracy publishes programs for Windows only, so on Linux everyone built them by hand. `mise run tracy-tools` now builds both from the pinned source, SHA-256 checked, into the checkout's `_deps/tracy-0.15.0/bin`. ## Breakdown - **Who it helps:** developers profiling the game on Linux (`LONGSHOT_TRACY=1` builds, [docs/development/tracy.md](docs/development/tracy.md)). - **What was wrong:** no Linux binaries of Tracy's tools exist, and a version other than 0.15.0 can't talk to the game's client. - **What changes:** a `tracy-tools` mise task: it downloads Tracy v0.15.0's source tarball, checks its SHA-256, builds `capture` and `csvexport` with cmake and ninja, and copies both programs to `_deps/tracy-0.15.0/bin` (inside the checkout, ignored as `_deps/` is; nothing global). A second run sees them and stops. The Capture section of tracy.md names the task. - **What does not change:** the game, its Tracy client (`third_party/tracy`), any build of the game, and the other tasks. - **How it was checked:** the task run from scratch on Linux: both programs built and captured from a `LONGSHOT_TRACY=1` game (a Castle Town Market capture, exported with `tracy-csvexport`); a second run said "already built". - **What is still open:** nothing. - **Risk:** low: a developer task, run only on request. ## Why Finding where the game's frames go, for the performance work, needed Tracy captures on Linux; the tools had to be built by hand from source, each time into a different place. A task makes that one command, into a folder of the checkout, at the one version that works. ## What changed - `mise.toml`: `[tasks.tracy-tools]` (Linux and macOS shells; it checks for cmake, ninja and c++ first and says which is missing). - `docs/development/tracy.md`: the Capture section names the task. ## Measurements Nothing to measure: a developer task that changes no build of the game. ### Flags and settings None. ## Testing **Tested:** CachyOS Linux: `mise run tracy-tools` from an empty `_deps/`: the tarball's checksum checked, both tools built (`_deps/tracy-0.15.0/bin/tracy-capture`, `tracy-csvexport`); `tracy-capture -a 127.0.0.1` took a capture from a `LONGSHOT_TRACY=1` game and `tracy-csvexport` read it; a second run stopped at "already built". **Not tested:** macOS (it should build the same way, untried). Windows has Tracy's own release programs; the task needs bash. `mise run test`: not run on this PC. **Must be tested:** - macos, by hand: `mise run tracy-tools` from an empty `_deps/`, expecting `tracy-capture` and `tracy-csvexport` in `_deps/tracy-0.15.0/bin` and `tracy-capture -a 127.0.0.1` connecting to a `LONGSHOT_TRACY=1` game ## Risks **What could break:** nothing outside the task. **Turning it off:** don't run it; or revert. **Compatibility:** Nothing changes: no option, cache or API. ## Checklist ### Everyone - [x] One topic. - [x] The title is a Conventional Commit (`type(scope): description`) of the status line's type. - [x] Why gives the reason plainly and links the issues that fit (the tracker searched). - [x] Tested on my own PC where it runs (in the game, for a change the game runs), as Testing's Tested says; what can't be run by hand is in Testing's Not testable by hand, with why. - [x] Measurements has a verdict, or one line saying why there is nothing to measure. - [x] Nothing gets worse that I know of: any cost (speed, latency, memory, a setup that worked before) is measured and in Risks. - [x] Testing names what was tested, what wasn't, and what must still be tested, where and how. - [x] Rebased on current `main`. - [ ] `python -I -B tests/run_all.py` passes (any failure that also fails on `main` is named). Not run on this PC. - [x] No game files, dumps, build output or generated files. - [x] `third_party/` untouched (a new folder with a `PROVENANCE.md` instead). - [x] The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled. ### When it applies - [x] AI assistance recorded with `Assisted-by:` / `Co-Authored-By:` trailers. - [x] Docs updated. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_016o1k1PazAdTJxQQWQBksW2
build(tracy): mise run tracy-tools builds tracy-capture and tracy-csvexport 0.15.0 into _deps
Some checks failed
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 10s
CI / Workflow lint (actionlint) (pull_request) Successful in 19s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 12s
Third-party parts / As their notes say (pull_request) Successful in 13s
Website / Website on Cloudflare (pull_request_target) Has been skipped
PR description / Description follows the template (pull_request_target) Failing after 3s
68ffc5f8b1
Tracy's releases have programs for Windows only, and the game's client
speaks 0.15.0's protocol alone: the task builds the capture and export
tools from the pinned source (SHA-256 checked) into the checkout's
_deps/tracy-0.15.0/bin, ignored as _deps/ is.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_016o1k1PazAdTJxQQWQBksW2
Member

Possibly related, for context:

  • PR #1543 feat(dev): LONGSHOT_TRACY=1 builds the game and the renderer with the Tracy profiler's zones, localhost only — Introduced Tracy profiling client and requires matching 0.15 tools
  • PR #1546 fix(dev): a Tracy build captures at full rate again (fibres off unless asked for), and the game-code zones give a valid capture — Fixed Tracy capture behavior using these tools
Possibly related, for context: - PR #1543 feat(dev): LONGSHOT_TRACY=1 builds the game and the renderer with the Tracy profiler's zones, localhost only — Introduced Tracy profiling client and requires matching 0.15 tools - PR #1546 fix(dev): a Tracy build captures at full rate again (fibres off unless asked for), and the game-code zones give a valid capture — Fixed Tracy capture behavior using these tools
HumanBean changed title from WIP: build(tracy): mise run tracy-tools builds tracy-capture and tracy-csvexport 0.15.0 into _deps to build(tracy): mise run tracy-tools builds tracy-capture and tracy-csvexport 0.15.0 into _deps 2026-11-19 14:59:38 +00:00
HumanBean deleted branch build/tracy-tools 2026-11-19 14:59:44 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot!1746
No description provided.