Repository navigation
Does not seem to work under Windows #14
Description
Hello,
When I run the following program with cabal run under Windows nothing happens.
hello-raylib> cabal run
hello-raylib>
hello-raylib.cabal
cabal-version: 3.4
name: hello-raylib
version: 0.1.0.0
common warnings
ghc-options: -Wall
executable hello-raylib
import: warnings
main-is: Main.hs
build-depends: base ^>=4.16.0.0
, h-raylib
hs-source-dirs: app
default-language: Haskell2010app/Main.hs
module Main where
import Control.Monad (unless)
import qualified Raylib.Core as Raylib
main :: IO ()
main = do
w <- Raylib.initWindow 480 320 "Hello, Raylib!"
let loop = do
shouldClose <- Raylib.windowShouldClose
unless shouldClose loop
loop
Raylib.closeWindow wI tried updating my NVidia drivers. No change.
I installed raylib and successfully ran one of their examples in C so I suspect there's something wrong with this package or something I've done or missed in the code posted above.
Thank you and kind regards
Björn
Activity
bjornkihlberg commentedon Mar 25, 2023
I tried running hello-raylib.exe inside dist-newstyle/build/x86_64-windows/ghc-9.2.1/hello-raylib-0.1.0.0/x/hello-raylib/\build/hello-raylib/ directly and I got this.
So it says (writing this for poor souls using a search engine)
which is a clue.
bjornkihlberg commentedon Mar 25, 2023
I got it to work with this solution.
The issue is that libwinpthread-1.dll is not available on the PATH when trying to run your raylib application. It looks like Windows users using Nim had the same problem.
Here are the steps I did explicitly:
C:\ghcup\msys64to my PATH which allows me to open themsys2executable. I don't think this is strictly needed but I did it so I'm writing it down here.C:\ghcup\msys64\mingw64\binwhich is actually needed for raylib to work.msys2and in it's shell ran this commandmsys2-keyringand then run another system update to make them work. Note that I didn't need to restart the shell this time!cabal runworked.My program behaved funny but it wasn't the fault of raylib. It was because I didn't invoke
beginDrawingandendDrawingwhich I assume polls the window for events.Anyway, I though I'd leave this here in case anyone else runs into this.
Anut-py commentedon Mar 25, 2023
Great, I'm glad you could find a solution! I'll add a link to this in the readme.