vasilito
90a264f1b1
Two related cleanups for the libdrm Rule 2 migration (commit5f5eec1c4): * libwayland: add -Dscanner=false to cookbook_meson, with a 20-line comment explaining the rationale. Without this flag, libwayland's meson.build builds a `wayland-scanner` executable for the *target* (Redox). The resulting binary has /lib/ld64.so.1 as its ELF interpreter (Redox's loader) and is useless on the build host. The pkgconfig that libwayland installs (wayland-scanner.pc) then points `wayland_scanner` to this Redox binary, and downstream consumers (mesa, wayland-protocols) pick it up via dependency('wayland-scanner'). When the cookbook's redoxer sandbox tries to exec it on the host, the host kernel can't find /lib/ld64.so.1 and the build fails with 'required file not found'. Disabling the scanner means libwayland doesn't install wayland-scanner to the sysroot. Downstream consumers then fall through to the host's /usr/bin/wayland-scanner (a proper x86_64-linux-gnu binary that works on the build host). This matches what wayland-protocols already does in its own meson.build (see its redox.patch in the recipe). * libdrm: remove 4 orphaned source-cache files that were left over from the libdrm Local source fork at local/sources/libdrm/ (deleted in commit5f5eec1c4). The 4 files were the in-tree Red Bear edits that are now external patches in local/patches/libdrm/: - source/virtgpu_drm.h DELETED (was in 01-drm-ioctl-bridge.patch) - source/xf86drm.c MODIFIED (most edits moved to patch) - source/xf86drmMode.c MODIFIED (most edits moved to patch) - source/xf86drm_redox.h DELETED (was in 01-drm-ioctl-bridge.patch) The local/recipes/libs/libdrm/source/ cache is now empty (only upstream files) and is regenerated by 'repo cook' from the upstream git URL specified in the recipe. These 4 files are no longer touched by the build system. Fixes the build correctness issue where downstream mesa/wayland-protocols builds would fail with 'required file not found: /lib/ld64.so.1' due to wayland-scanner being built for the wrong target. The fix mirrors what upstream Redox's wayland-protocols recipe does in its own meson.build.
libdrm - userspace library for drm
----------------------------------
This is libdrm, a userspace library for accessing the DRM, direct rendering
manager, on Linux, BSD and other operating systems that support the ioctl
interface.
The library provides wrapper functions for the ioctls to avoid exposing the
kernel interface directly, and for chipsets with drm memory manager, support
for tracking relocations and buffers.
New functionality in the kernel DRM drivers typically requires a new libdrm,
but a new libdrm will always work with an older kernel.
libdrm is a low-level library, typically used by graphics drivers such as
the Mesa drivers, the X drivers, libva and similar projects.
Syncing with the Linux kernel headers
-------------------------------------
The library should be regularly updated to match the recent changes in the
`include/uapi/drm/`.
libdrm maintains a human-readable version for the token format modifier, with
the simpler ones being extracted automatically from `drm_fourcc.h` header file
with the help of a python script. This might not always possible, as some of
the vendors require decoding/extracting them programmatically. For that
reason one can enhance the current vendor functions to include/provide the
newly added token formats, or, in case there's no such decoding
function, to add one that performs the tasks of extracting them.
For simpler format modifier tokens there's a script (gen_table_fourcc.py) that
creates a static table, by going over `drm_fourcc.h` header file. The script
could be further modified if it can't handle new (simpler) token format
modifiers instead of the generated static table.
Compiling
---------
To set up meson:
meson builddir/
By default this will install into /usr/local, you can change your prefix
with --prefix=/usr (or `meson configure builddir/ -Dprefix=/usr` after
the initial meson setup).
Then use ninja to build and install:
ninja -C builddir/ install
If you are installing into a system location you will need to run install
separately, and as root.