Skip to content
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

Created a simple windows binary package. #47

Merged
merged 1 commit into from
Sep 21, 2020
Merged

Conversation

Martinsos
Copy link
Member

It almost works!
So, the idea is that you unpack created zip on Windows, and then you just run wasp.ps1 script via powershell and there you have it!
wasp new myapp works, but wasp start fails when it tries to run npm start, saying it can't find npm. But that is weird because it can find node, and I had both node and npm installed in the path.
Maybe some dynamic libraires are missing and this is how it is manifesting? Maybe StreamingProcess does not work but just Process works in Haskell on Windows?
Best would be to actually install stack on windows and compile and try out stuff, see if it works like that, what does or does not work and so on.

`wasp start` fails at calling `npm` (can't find it).
@Martinsos Martinsos merged commit f13101e into master Sep 21, 2020
@Martinsos Martinsos deleted the windows-package branch September 21, 2020 13:52
@WilliamRagstad
Copy link

Often when running installation Powershell scripts, they're called install.ps1.
Maybe renaming it will make the purpose clear?

@Martinsos
Copy link
Member Author

Are you referring to run_wasp.ps1, @WilliamRagstad ? If so, that one is not an installation script actually, it is a "proxy" that calls the binary with the correct configuration (correct env vars).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants