[jordanella]

When a build translates the game again (about 5 minutes on Windows) there was no way to see why beyond "the key changed", and a build started any other way than make_game.py's own had another environment, so other object and lift keys. This adds one entry point for developers, nx2/dev.py, and puts the build's environment in one place. The dev-loop proposal's A9 (#2636); its later pieces (scenario runs, where, the bench lock, warnings) build on it.

Stacked on #2874 (the lift key's environment, its first commit here): review the last three commits; this rebases to them alone once #2874 is in.

Change

• nx2/profiles.py (new): the environment the lift and build.py run with, the dictionary make_game.py built in place, in two profiles: release (the builders') and dev (HOOKSHOT_PROFILE=dev: no RX_RELEASE, so a console and no shader preparation at start; the lift is the same, since feat(build): the lift key hashes only the environment that changes the lifted C #2874's key no longer hashes RX_RELEASE).
• nx2/make_game.py: takes it from there, and records how it was started in <work>/last_build.json: its arguments, its Python, the profile, the toolchain's variables. lift_key keeps what each key was made of (the Python, the HLE functions, each file's hash by name, the variables), and write_lift_key writes the stored key's parts to <work>/sa/lift_key_parts.json, outside gen/.
• nx2/dev.py (new, standard library only):
  • status: whether the next build skips the lift, and if not, which file, HLE function, variable or Python changed;
  • times [-n N]: the last builds' phases side by side (feat(build): build_times.json and the build's last lines say where the time went #2693's build_times.json);
  • build [--dev]: the last build again, with its arguments, Python and tools (its --log left out);
  • compdb: the last build's compile_commands.json (perf(build): skip unchanged links, write compile_commands.json, key the hot pieces by the profile's contents #2893) at the checkout's top, for clangd.

Nothing it prints comes from the game's files: names, times and hashes of the tools' own inputs.

In use

Windows 11, in a work folder with a translation:

• dev.py status after A64_NO_VFPX=1 in the shell: lift: the next build translates the game again: then environment A64_NO_VFPX: (unset) -> 1.
• dev.py build replayed the last build (the same arguments and Python, shown quoted).
• dev.py times -n 3 showed the last builds' phases side by side.
• The game from these builds plays: in Kokiri Forest from a save, RTX 3080 (NVIDIA 621.14), 28-31 fps, nothing in the log about a lost device or a crash.

Testing

• tests/test_dev_tool.py (new): the differences status names (a file, a variable, the Python, an HLE function), the work folder it picks, times' table, build's replayed command (without --log) and its environment for each profile, compdb.
• tests/test_lift_cleanup_error.py: takes write_lift_key's new globals.
• Every check that reads the changed files (55), through run_all.py, rebased on today's main, Windows: 54 pass; test_linux_update fails the same way on main here.
• Not tested: Linux.

See #2636 (A9), #2874.

🤖 Generated with Claude Code