-
Notifications
You must be signed in to change notification settings - Fork 103
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
Building on Windows #141
Comments
Unfortunately there are quite a few other breaking changes in that Oclif update that would need handling first to make this possible, but I'm definitely interested in going in that direction though if we can so you're welcome to investigate if you're interested. I've had oclif/oclif#828 for example in my todo list for a long while but I've never found time to look into it properly. What's the state of this if you build on Windows currently, does it just fail unavoidably? |
The current version of Oclif will refuse to run on windows. And just upgrading these libs is not possible. There are changes to do before that. 3 majors versions is a little bit too much :) But upgrading to the latest version of oclif/command is possible without any problem. oclif/core is what replace oclif/command, but I didn't try to go further that oclif/command for now |
Ok, it seemes that I was a little bit too exited to see that, indeed, you could build for windows, and get the installer, but you can't "pack"... |
Hey Tim, I've been thinking about this for a long time, and Oclif is now able to build (and pack) on windows, so here we are...
Would it be interesting to make the build compatible between windows/linux?
I've done a few tests and according to the Oclif example, here's which version Httptoolkit-server should have:
I only include what should be updated for the sake of brievity
full package.json
I'm ok to write a PR for that because I know it's boring stuff
The text was updated successfully, but these errors were encountered: