Build failure on OS X

[blitzcode]

Hello,

I'm seeing the following issues when installing GLFW-b on OS X 10.6 / HP 2013.2.0.0 using cabal:

[1 of 1] Compiling Bindings.GLFW ( dist/build/Bindings/GLFW.hs, dist/build/Bindings/GLFW.p_o )
...
glfw/src/cocoa_window.m:77:0: error: incompatible types in return
glfw/src/cocoa_window.m: In function ‘createWindow’:
...
cabal: Error: some packages failed to install:
GLFW-b-1.1.0 depends on bindings-GLFW-0.0.1 which failed to install.
bindings-GLFW-0.0.1 failed during the building phase. The exception was:
ExitFailure 1

Is there anything I can do to fix this?

I already installed the 'non-b' GLFW package before and successfully compiled and ran a short example. I'm fairly clueless here, but I was surprised to learn that both bindings use the same module name, 'Graphics.UI.GLFW'. Is it possible to have them both installed at the same time, or am I causing problems by doing so?

Would love to try out GLFW-b, any fixes/help greatly appreciated!

[bsl]

Hi, sorry about the problem. I don't know what to think about that error. I don't have any OS X systems to test on. If you find out what was wrong, please post here about it.

It's fine to have GLFW and GLFW-b installed at the same time. It's not a problem that the modules have the same name.

[blitzcode]

It looks like the people at GLFW already have a patch for this exact problem:
kylemcdonald/glfw@f03d999

I applied those changes to the GLFW sources in your binding package, and it now builds and installs fine. I installed the main GLFW-b package after that and was able to compile & run your GLFW-b-demo program. Would be great if you could bump GLFW-internal to whatever version contains that 10.6 fix for cocoa_window.m!

[bsl]

I'm glad to hear you found a fix. But bindings-GLFW already binds to the latest release of GLFW, and I'm not seeing that patch in the official GLFW repo (https://github.com/glfw/glfw). You might add an issue there so that they can evaluate whether they should apply that patch.

[blitzcode]

It seems like they found a better solution:

glfw/glfw#74

I guess the next release of GLFW should have it fixed. In any case, thanks for your help and I'll directly report any further issues like this to the GLFW team.