linux builder: honor HOOKSHOT_JOBS before selecting workers #505
No reviewers
Labels
No labels
accessibility
autorelease: pending
autorelease: tagged
bug
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
question
testing wanted
wontfix
No milestone
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Hookshot!505
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/linux-gui-build-jobs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem and behavior
Fixes #494. The Linux AppImage's builder chose its worker count using the legacy
RX_JOBS/memory fallback, then passed explicit--jobs. That overrode the documentedHOOKSHOT_JOBSsetting even when the AppImage inherited it correctly.Honor a positive
HOOKSHOT_JOBSvalue before constructing the build command. Unset, empty and zero keep the exact existingtoolchain.default_jobs(3.5)fallback, includingRX_JOBS. Negative or nonnumeric values show a clear error before configuration writes, progress, process or thread startup. CLI behavior is unchanged. Document launching from the same terminal and distinguish build settings from the game'shookshot_env.txt.Checks
Builder.buildmethod and real production helper without importing Tk. They record the generated command, configuration writes, progress, process/thread calls and fallback argument. All seven pass on Windows; the original method failed the positive override and both invalid-input checks.make_game.py. No Tk or GUI execution. Existing CLI source and the legacy toolchain remain unchanged.Limits
No SteamOS/AppImage GUI or real game/native build was run. All four hosted checks passed at
a529984: Windows and Linux source checks, SPIR-V emission and AppImage packaging. Automatic worker selection and compiler memory policy are unchanged.