On 2015-06-24 10:22, Husk 00 wrote:
Is this bug traced on the wiki? There is a way to know if/when it will be solved?
not in the wiki. in the issue-tracker: https://github.com/umlaeute/Gem/issues/87
finally:
afair glfw3 has support for context-sharing, and it (the glfw3 demo showing this feature) doesn't seem to crash on intel cards. which hints that the bug is really with Gem (not the drivers). i can't remember the state of the [gemglfw3window] regarding context sharing.
I want to test gemglfw3window with my drivers but I had this error: /usr/lib/pd/extra/Gem/gemglfw3window.pd_linux: undefined symbol: glfwSetCursorPosCallback
according to [1], the function is in glfw3. so either it's a transient bug in glfw3 or...
GLFW3 was compiled from source (git repo). Gem was configured with "--with-glfw3-CFLAGS=/usr/include/GLFW/ --with-glfw3-LIBS=/usr/lib/" flags.
...your build-flags told Gem not to link against libglfw.
if you must pass --with-glfw3-*FLAGS, then you should use: "--with-glfw3-CFLAGS=$(pkg-config --cflags glfw3) --with-glfw3-LIBS=$(pkg-config --libs glfw3)"
but really, Gem should detect glfw3 automatically (did you try that?)
fgmasdr IOhannes