-
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
Stack compiling GTK project #3810
Comments
|
yes, that' right, all the stack "incantation" run smoothly (stack setup, stack build). BTW I fight a lot with dependencies in packages gio against gtk (if I remember well) finally I get to match the proper version this is my stack.yaml extract :
|
@ImreMD see workaround here: https://github.com/haskell-gi/haskell-gi/wiki/Using-haskell-gi-in-Windows |
Anrock thank you very much, that's working! I suspected that Stack hasn't the proper zlib when running out of the runghc ecosystem, but I am not aware of the internals and do not know from where should I move this zlib1.dll (windows system? stack but where etc... There is a bunch of zlib1 files on a Windows computer). |
Sounds like this was resolved, closing |
Hello, I have a question related to GTK compiling (note: I am under Windows 10 x64) the program is compiling without problem it's a very simple program just poping a GTK window that's all. When I run it with stack runghc (in a stack shell/ecosystem as I understand) the window appear and everything is fine, but when I try the same with stack exec I have an error message saying: "the procedure entry point inflatValidate could not be located in the DLL ... blah blah ... libpng16-16.dll" . It's probably related to an improper linking of library during compilation, but why it is working in the Stack shell? The stack environment has the good library already linked? Why it cannot use the same set of file during linking/compiling? If needed I can attach the config file or some other information. May be someone encounters the same error.
IM
The text was updated successfully, but these errors were encountered: