when running roguestar I get an error like so for both ./roguestar
./roguestar -v -s
starting process: ~/Library/Haskell/ghc-7.0.2/lib/roguestar-0.6.0.1/bin/roguestar-engine +RTS -RTS version over begin
roguestar: src/Main.hs:(154,17)-(156,59): Non-exhaustive patterns in case
I believe that this is caused by not having the client installed. 'cabal install roguestar-glut'?
Nope that didn't fix it.
Those are the line numbers that try to locate roguestar-glut or roguestar-gtk. Why does it say it's calling /bin/roguestar-engine?
This is on OS X? Something's going on where it doesn't have a good filesystem path. I wonder if there's somewhere I can get an OS X cloud instance or something.
yes this is on OSX. all haskell packages are here installed by default under
so I have now (I am compiling roguestar 0.7 now)
and several other packages like rsagl etc. I tried adding the above to the path but still roguestar gives the Non-exhaustive patterns... I am trying to look at the code to see how exactly it tries to locate glut. Cause I can run roguestar-glut seperately which just brings a window with "waiting for engine" message. It is possible the function to find if file exists is platform specific.
Don't think there are osx cloud instances though. :(
But I can test it and let you know :).. Just buzz me if you want me to try something specific.
Ok I just discovered the prefix p option to roguestar and tried to launch it
roguestar -s -1 -e -p -v ~/Library/Haskell/ghc-7.0.2/lib/roguestar-glut-0.7.0.0/bin/
which prints a lot of surface loaded messages and opens the glut window which seems to hang..
am I giving the correct arguments?
ok I soft linked the engine in the same directory as where the roguestar-glut is which I have given as the prefix. Now I get the species selection screen. Yay.
Unfortunately this screen still hangs ignoring any key press. :(
I can only guess -- click in the window to give it focus? Failing that, if you use --echo-protocol, this should print client-server traffic, which should happen in bursts every time you issue a command.
Due to architectural changes, this bug is unlikely to by applicable to the upcoming release. Closing.