-
Notifications
You must be signed in to change notification settings - Fork 842
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: stack exec foo
works, foo.exe does not
#425
Comments
Most likely Windows is not able to find the necessary C++ libraries from the standard prompt because they're not on your PATH.
In theory, stack could copy some DLLs over to the output directory for you, but that seems out-of-scope for what it's doing. |
Cool, thanks. I assume these libraries are created by stack during |
Actually, they're not, they're shipped with GHC (and, theoretically in some cases, MSYS). The easiest way to find them is
|
If that turns out to resolve it for you, would you be able to add a FAQ entry on the Wiki about this? |
perhaps an idea for a future plugin: bundle up a self-contained windows executable or installer? |
Sounds like what we're doing with docker. Mind opening as a separate issue? On Fri, Jun 26, 2015, 6:28 PM Christopher Armstrong <
|
Done |
Thanks! |
On windows
stack build
andstack exec foo
works (which is great, btw). My program is running.However, after
stack install
the execution of the executable file fails.I have no understanding of what
stack exec
does in windows (magic?). Any hint to what's going on?The text was updated successfully, but these errors were encountered: