Allow exported apps on windows to be run from anywhere on the system #1314
Conversation
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
…instead of requiring it to be in the same folder as the executable
Stefterv
approved these changes
Nov 27, 2025
Collaborator
|
Hi @jSdCool Thanks for this quick fix, I tested it on Windows just now and indeed allows the sketch to be run from any working dir! Thanks! |
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.
On Linux and Macos an exported sketch can be run from any working directory. Until now that has not been the case on windows. This was caused by the EXEDIR environment variable not being used when forming the class path. This pr makes that simple change, allowing the executable generated from exporting a sketch to be executed on the command line from any working directory.