mirror of
https://github.com/tangerineturtle1/NX2navi.git
synced 2026-11-19 12:59:58 -04:00
Check the disk space and the build tools before the long steps.
Only the RomFS image's space was looked at, and only when that step began: a disk that held the image but not the build cache or the shaders stopped the build in the compile or, half an hour in, in the shader preparation. The build now adds up what the steps it will run write into the game folder (the image and 1 GiB, 2 GiB for the build cache, 4 GiB for a full shader preparation, the least each is known to need) and stops at once when the disk has less, naming each part and how much is missing. On Windows a build whose compile step will run first compiles and links an empty program with the installed tools, against the libraries the game links. Tools that are incomplete or blocked stopped the build only in its compile step, after the image and the lift; the message says what failed and how to get the tools back. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
@@ -125,7 +125,11 @@ A path the Windows ANSI code page cannot hold breaks the MSYS2 tools, so the too
|
||||
complete. No MSYS2 shell or pacman runs. Then zbic: the wheel for the bundled Python from PyPI, checked against
|
||||
PyPI's sha256, into `pydeps/`.
|
||||
2. **Inspect Your Game** to **Compile**: `tools/make_game.py --nup <dump> --out <game> --msys <toolchain> --events`,
|
||||
whose `@@` progress lines drive the rows (check, exefs, romfs, lift, compile). How it keeps the build short:
|
||||
whose `@@` progress lines drive the rows (check, exefs, romfs, lift, compile). Before the first long step it
|
||||
looks at what can be known to fail later: the disk space of every step that will run (the RomFS image and 1 GiB,
|
||||
2 GiB for the build cache, 4 GiB for the prepared shaders; `check_space` names each part and how much is
|
||||
missing), and that the build tools compile and link an empty program (`probe_toolchain`). How it keeps the build
|
||||
short:
|
||||
- The RomFS image (26 GB, mostly disk work) is packed beside the lift and the compile (processor work), so a first
|
||||
build takes about as long as the longer of the two. Only `romfs.c`, which includes the RomFS index's
|
||||
`romfs_config.h`, waits for the image.
|
||||
|
||||
Reference in New Issue
Block a user