fix: support mise et al on windows #304
Merged
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
doorgan
force-pushed
the
doorgan/windows-issues
branch
from
380efb8 to
9f9c5c7
Compare
doorgan
force-pushed
the
doorgan/windows-issues
branch
from
8c8ad45 to
7fe0927
Compare
doorgan
force-pushed
the
doorgan/windows-issues
branch
from
7fe0927 to
7ad4f2e
Compare
mhanberg
approved these changes
Jan 14, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #266
When fixing this I also found these issues:
just releasefailed to start the engine because it tried to load bootfiles from the plain release. The fix is to remove the release directory from the windows PATH similarly to how we reset the PATH for unix, and to remove theERLEXEC_DIRenv varcmd.exe. Apparently, using:spawn_executabledirectly doesn't work with batch scripts on windows because they're not proper executableserror starting node: {{:shutdown, {:failed_to_start_child, XPForge.EPMD, {:EXIT, {:undef, [{XPForge.EPMD, ...error. This was caused by paths using inconsistent separators\\vs/, causing the namespacing code to not find any.beamfile, thus not namespacing anything. Normalizing the paths fixes that. I'm not sure why this issue in particular manifests when using mise, I wasn't able to reproduce it with my globalscoopinstalled elixir.