-
-
Notifications
You must be signed in to change notification settings - Fork 60
feat: windows support #219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
doorgan
wants to merge
13
commits into
main
Choose a base branch
from
doorgan/windows-support
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
This comment was marked as outdated.
This comment was marked as outdated.
mhanberg
reviewed
Nov 19, 2025
This comment was marked as resolved.
This comment was marked as resolved.
43c27ad to
c938c4a
Compare
mhanberg
reviewed
Nov 20, 2025
Collaborator
Author
doorgan
commented
Nov 21, 2025
Comment on lines
-168
to
-180
| defp app_globs do | ||
| app_globs = Enum.map(@allowed_apps, fn app_name -> "/**/#{app_name}*/ebin" end) | ||
| ["/**/priv" | app_globs] | ||
| end | ||
|
|
||
| def glob_paths(_) do | ||
| entries = | ||
| for entry <- :code.get_path(), | ||
| entry_string = List.to_string(entry), | ||
| entry_string != ".", | ||
| Enum.any?(app_globs(), &PathGlob.match?(entry_string, &1, match_dot: true)) do | ||
| entry | ||
| end |
Collaborator
Author
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Windows was not finding the files on windows with the old code
3b99b09 to
c476bd9
Compare
I got tired of building burrito releases on windows
This is the same method Livebook uses for the very same reasons
0f11f1a to
9269f26
Compare
Member
|
Is this ready for review? |
Collaborator
Author
|
@mhanberg almost, there's a few failing tests on windows I'm fixing. I'll tag you when it is. |
9269f26 to
bf7cb5f
Compare
86651c4 to
1e93243
Compare
Collaborator
Author
|
@mhanberg it's ready for review now! |
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.

Adds support for Windows
Closes #89
Fixes #60
Also adds a
just start-tcptask to start a plain release in TCP mode for development because expert builds burrito releases SO SLOW on my windows machine that it spent more time waiting for the build than actually working on the relevant changesOne note here is that this implementation uses the user's globally installed elixir on Windows. I don't know if there's any version manager like mise/asdf/nix on windows, if there is we'll need to get the PATH for the project folder like we do for Unix
Another note is that for reasons I don't yet understand windows is way slower than unix even on my beefy machine, so I had to increase the timeouts for a few tests. I was also seeing a few timing issues due to this that I hope were reliably mitigated.