f31522130f
Build system (5 gaps hardened): - COOKBOOK_OFFLINE defaults to true (fork-mode) - normalize_patch handles diff -ruN format - New 'repo validate-patches' command (25/25 relibc patches) - 14 patched Qt/Wayland/display recipes added to protected list - relibc archive regenerated with current patch chain Boot fixes (fixable): - Full ISO EFI partition: 16 MiB → 1 MiB (matches mini, BIOS hardcoded 2 MiB offset) - D-Bus system bus: absolute /usr/bin/dbus-daemon path (was skipped) - redbear-sessiond: absolute /usr/bin/redbear-sessiond path (was skipped) - daemon framework: silenced spurious INIT_NOTIFY warnings for oneshot_async services (P0-daemon-silence-init-notify.patch) - udev-shim: demoted INIT_NOTIFY warning to INFO (expected for oneshot_async) - relibc: comprehensive named semaphores (sem_open/close/unlink) replacing upstream todo!() stubs - greeterd: Wayland socket timeout 15s → 30s (compositor DRM wait) - greeter-ui: built and linked (header guard unification, sem_compat stubs removed) - mc: un-ignored in both configs, fixed glib/libiconv/pcre2 transitive deps - greeter config: removed stale keymapd dependency from display/greeter services - prefix toolchain: relibc headers synced, _RELIBC_STDLIB_H guard unified Unfixable (diagnosed, upstream): - i2c-hidd: abort on no-I2C-hardware (QEMU) — process::exit → relibc abort - kded6/greeter-ui: page fault 0x8 — Qt library null deref - Thread panics fd != -1 — Rust std library on Redox - DHCP timeout / eth0 MAC — QEMU user-mode networking - hwrngd/thermald — no hardware RNG/thermal in VM - live preload allocation — BIOS memory fragmentation, continues on demand
31 lines
1.3 KiB
Markdown
31 lines
1.3 KiB
Markdown
# Wayland
|
|
|
|
Wayland is a project to define a protocol for a compositor to talk to
|
|
its clients as well as a library implementation of the protocol. The
|
|
compositor can be a standalone display server running on Linux kernel
|
|
modesetting and evdev input devices, an X application, or a wayland
|
|
client itself. The clients can be traditional applications, X servers
|
|
(rootless or fullscreen) or other display servers.
|
|
|
|
The wayland protocol is essentially only about input handling and
|
|
buffer management. The compositor receives input events and forwards
|
|
them to the relevant client. The clients creates buffers and renders
|
|
into them and notifies the compositor when it needs to redraw. The
|
|
protocol also handles drag and drop, selections, window management and
|
|
other interactions that must go through the compositor. However, the
|
|
protocol does not handle rendering, which is one of the features that
|
|
makes wayland so simple. All clients are expected to handle rendering
|
|
themselves, typically through cairo or OpenGL.
|
|
|
|
Building the wayland libraries is fairly simple, aside from libffi,
|
|
they don't have many dependencies:
|
|
|
|
$ git clone https://gitlab.freedesktop.org/wayland/wayland
|
|
$ cd wayland
|
|
$ meson build/ --prefix=PREFIX
|
|
$ ninja -C build/ install
|
|
|
|
where PREFIX is where you want to install the libraries.
|
|
|
|
See https://wayland.freedesktop.org for documentation.
|