-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Windows support #47
Labels
Comments
In the time since I opened this issue, I am now primarily developing on a Windows machine with WSL. How the times have changed. 😄 The test suite is mostly passing, but I'm stuck on getting the |
zombiezen
added a commit
that referenced
this issue
Sep 7, 2020
zombiezen
added a commit
that referenced
this issue
Sep 7, 2020
Because we're using Bash on all platforms, this means that we shouldn't be doing a platform-dependent switch. Explicitly naming functions after Bash helps make it clear that this is desired behavior. Updates #47
zombiezen
added a commit
that referenced
this issue
Sep 7, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be nice to have Windows support. While I don't develop on Windows regularly, I feel confident enough in the test suite that if I start running Windows in CI (probably using AppVeyor) that it would work fairly well. Shipping Windows binaries would be easy at that point.
The text was updated successfully, but these errors were encountered: