Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Avoid depending on libwayland 1.20 unnecessarily
When linking to Wayland libraries in the normal way instead of loading them dynamically at runtime, listing symbols that don't exist in the current version results in a build failure. Most of these symbols are things we call directly, so we want to have them available as often as possible. However, we don't actually call wl_proxy_marshal_flags() or wl_proxy_marshal_array_flags() directly. The reason we need them is that they're called by the code generated by wayland-scanner >= 1.20. If we're building with an older Wayland library, then we'll presumably have its corresponding version of wayland-scanner, so we won't need those two symbols, and can avoid generating a dependency on them. libwayland 1.18 is in several LTS distributions (Ubuntu 20.04, Debian 11, RHEL 8) so avoiding a hard dependency on 1.20 is quite useful. Signed-off-by: Simon McVittie <[email protected]> Resolves: #5376
- Loading branch information