Repository navigation
Use -o rather than the undocumented --executable on Linux/macOS - #4
Merged
DNSGeek merged 1 commit intoOct 1, 2026
Conversation
PureBasic's own reference documents the output switch as "-o, --output, /OUTPUT <filename>" and the Windows example uses /EXE, but "--executable" appears nowhere: not in `pbcompiler -h` and not in the manual. It is accepted by 6.41 and does honour the path, so this is not a live bug -- it is an undocumented alias with nothing promising it on other versions. -o is the same switch in its documented short form, so the non-Windows branch now uses it. The /EXE choice for Windows is unchanged and matches the manual's Windows example.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Based on
claude/issue-1-20260930-0310, so this is a one-line amendment to #3 rather than a competing fix — merging it updates that PR, which then carries the whole correction tomain.What changes.
--executable→-ofor the non-Windows branch./EXEon Windows is untouched.Why. PureBasic's reference documents the output switch as
-o, --output, /OUTPUT <filename>.--executableappears nowhere: not inpbcompiler -hon 6.41, and not in the manual. I checked that 6.41 does accept it and does write to the path it is given, so this is not a live bug — it is an undocumented alias, with nothing promising it on another version or platform.-ois the same switch in its documented short form: it is the one the switch table lists, and the one the manual's Windows example pairs with/EXE.Checked.
npm install && npm run compile→tsc -p ./exits 0 on this branch. Unlike the original patch, this has been through the type-checker.I could not test the Windows
/EXEpath — no Windows here. Worth noting the manual is inconsistent about it: the cross-platform table gives/OUTPUT, while the Windows example uses/EXE "C:\Project\project.dll". Presumably both are accepted, but that branch still wants a run on Windows before merge.