New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implementation for Wayland #106

Closed
MyZeD opened this Issue Aug 2, 2013 · 9 comments

Comments

Projects
None yet
5 participants
@MyZeD

MyZeD commented Aug 2, 2013

We should go with the future and build a interface for Wayland...

@elmindreda

This comment has been minimized.

Member

elmindreda commented Aug 4, 2013

Definitely.

@siavashserver

This comment has been minimized.

Member

siavashserver commented Aug 13, 2013

I would wait for Mir vs. Wayland winner, before making decisions. They are not ready for real world yet.

Also don't forget about hardware manufacturers; There is no point in adding support for a backend which is not going to receive proprietary driver support.

@elmindreda

This comment has been minimized.

Member

elmindreda commented Aug 15, 2013

I would wait for Mir vs. Wayland winner, before making decisions. They are not ready for real world yet.

There is no decision to make. Both will need to be supported. While Mir is a very bad idea, Canonical will still ram it down everyone's throats and Steam targets Ubuntu above other distros. I'll likely write the support for at least whichever one ends up on my system and I welcome patches for either one.

Also don't forget about hardware manufacturers; There is no point in adding support for a backend which is not going to receive proprietary driver support.

Mir has already been promised support by hardware vendors, and both it and Wayland already run on the various Mesa hardware drivers. This is quite enough for GLFW to be useful.

@jadahl

This comment has been minimized.

Contributor

jadahl commented Mar 18, 2014

Made a pull request with a beginning of a Wayland backend: #256

@elmindreda

This comment has been minimized.

Member

elmindreda commented Mar 21, 2014

The Wayland work by @jadahl now lives in the wayland branch.

@BrettRToomey

This comment has been minimized.

BrettRToomey commented Mar 27, 2014

Has anyone planned on doing Mir work? Our products depend on GLFW and we definitely need Ubuntu support. If no one has yet, I'm willing to work on a mir branch. Of course, Mir isn't finished yet, so it'll just have to be the skeleton until Mir is ready.

@elmindreda

This comment has been minimized.

Member

elmindreda commented Mar 28, 2014

@Team5D It's planned but no code has been written, so please do! Base it on the wayland branch, as that contains work making it easier to re-use non-X11 parts of the Unix specific code.

@elmindreda

This comment has been minimized.

Member

elmindreda commented Apr 8, 2014

The Wayland work has been merged. I'm leaving this open as the current Wayland work is far from complete. I merged it to 3.1 for ease of access and to get the increased modularity. The modularity will be useful for other things such as alternative joystick implementations.

Wayland support is disabled by default and won't be advertised as a new port for 3.1.

@Team5D It's now safe to base your Mir work on master.

@elmindreda elmindreda added Wayland and removed X11 labels Jun 29, 2014

@elmindreda

This comment has been minimized.

Member

elmindreda commented Jun 29, 2014

A large chunk of Wayland work by @jadahl was just merged to master.

@elmindreda elmindreda closed this Oct 22, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment