I don't think there is anything fundamentally limiting to being able to
implement GLFW 3. We have a label in the bug tracker specific to GLFW, see
https://github.com/kripken/emscripten/labels/GLFW which you can use to
track the progress. There is a contributor Jari Vetoniemi who's been
championing the GLFW update from version 2 to 3. Contributions, issue
reports and pull requests towards this are welcome!

Jukka


2014-08-29 20:19 GMT+03:00 Robert Goulet <[email protected]>:

> At the time of writing this, Emscripten 1.22.0 currently ships with GLFW
> 2.7.7. This is causing problems:
>
>
>    1. The GLFW API of the 3.x serie is quite different, as noted on this
>    web site <http://www.glfw.org/docs/3.0/moving.html>. This makes the
>    code less portable because two versions of GLFW must be used if the
>    application also targets Linux.
>    2. The GLFW main header file automatically includes gl.h and glext.h.
>    Because of this, including Emscripten glfw.h erronously includes
>    standard OGL headers instead of their OGLES2 variants. This is not an issue
>    in GLFW 3.x as seen here
>    <http://www.glfw.org/docs/latest/glfw3_8h_source.html> because we can
>    define GLFW_INCLUDE_ES2.
>
> Besides, the GLFW 3.x API seems much better and easier to use. So I am
> wondering, is there anything that prevents Emscripten from upgrading to
> GLFW 3.x? Is this something already planned? I am considering doing the
> upgrade myself, but I was just curious what is the status of this. Thanks!
>
> --
> You received this message because you are subscribed to the Google Groups
> "emscripten-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to