Wayland FAQ

원본 사이트

• Why fork the X server?
• What is the license?
• Why duplicate all this work?
• What is the drawing API?
• Is wayland replacing the X server?
• Why not extend the X server?
• What is wrong with X?
• What about the overhead of running X on wayland?
• Is Wayland network transparent / does it support remote rendering?
• How to download and build Wayland?
• Why wasn't D-Bus used instead of the Wayland IPC mechanism?
• How can I replace Wayland's Window Manager?
• Why does Wayland use EGL?

Why fork the X server?

-  컴포지터와 클라이언트 간의 프로토콜이다. 컴포지터가 클라이언트들에게 입력 이벤트를 보낸다. 

What is the license?

- Wayland : MIT 라이센스에 GPL

Why does Wayland use EGL?

- EGL is the only GL binding API that lets us avoid dependencies on existing window systems, in particular X. GLX obviously pulls in X dependencies and only lets us set up GL on X drawables. The alternative is to write a Wayland specific GL binding API, say, WaylandGL.

A more subtle point is that libGL.so includes the GLX symbols, so linking to that library will pull in all the X dependencies. This means that we can't link to full GL without pulling in the client side of X, so Weston uses OpenGL ES to render. This also enables Weston to run on GPUs which don't support the full OpenGL API.

As detailed above, clients are however free to use whichever rendering API they like.

Weston uses OpenGL ES to render