-
Notifications
You must be signed in to change notification settings - Fork 12
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
using sdl2: can't load .so/.DLL for: mingw32.dll #28
Comments
okay sorry for the noise, it's a known bug. https://ghc.haskell.org/trac/ghc/ticket/3242 |
Sorry to hear that, not much for us to do then. |
Note that this bug is specific to 64-bit GHC (and the reason I'm using 32). If you can make that switch, also see here for how to avoid a bug on the SDL2-devel library side. |
@tejon thank you very much for this information. I will consider now to switch to 32bit! |
sorry for the noise again: like above but with x32 pathes:
results in this error:
and a windows error dialog pops out with the error code |
The x86_64 mingw lib path looks suspicious. Cheers,
|
@Kludgy sorry was a c&p error, I corrected it just a minute after hitting the comment button. |
Hi it's me again with a similar problem as in #5
I'm trying to use the sdl2 package on windows (mostly for developing in (quine)[ekmett/quine]). After some pitfalls I'm able to build the
sdl2
package from source and from hackage. My current build flow:SDL2-devel-2.0.3-mingw.tar.gz
from https://www.libsdl.org/download-2.0.php intoC:\SDL2-2.0.3
cabal get sdl2
cd sdl2
cabal configure --extra-include-dirs="C:\\SDL2-2.0.3\\include" --extra-lib-dirs="C:\\SDL2-2.0.3\\x86_64-w64-mingw32\\lib"
cabal build
the build is successful but using the lib in an other project results in a build error:
the relevant lines from the SDL pkg-config:
I believe that there is no mingw32.dll in MinGW. A wild guess: something tries to link dynamically while it should linked statically?
related on SO: http://stackoverflow.com/questions/15996796/haskell-sdl-cant-find-mingw32-dll
I'm a bit lost here. Is this really a ghc bug? Should I report it there? Or is this a bug of this bundle. I'm using the GHC 7.8.4 (64-bit) version of MinGHC.
The text was updated successfully, but these errors were encountered: