fix: add platform-specific executable extension to build output paths #158
+8
−5
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.
• Import exeExtension from Distribution.Simple.BuildPaths to determine
correct executable naming by platform
• Extract platform information from toolchain configuration during build
orchestration
• Apply platform-specific file extension (e.g., .exe on Windows) when
constructing executable paths in build output
• Refactor variable naming for clarity (exe → exeName) to distinguish
filename base from full executable path
• Normalize import formatting for consistency