Jan Beich

Can you document `xwayland scale ` in sway/sway.5.scd? Also, `-Dxwayland=false` build fails (see f98ca3ab7ca1 for a rough fix): ```c++ ../sway/commands/xwayland/scale.c:23:12: error: no member named 'xwayland' in 'struct sway_server' if(server.xwayland.wlr_xwayland !=...

`` is supported via libexecinfo on musl and BSDs. Duplicate of https://github.com/intel/compute-runtime/issues/331 but proposes a different fix.

I confirm, works fine after e08bd1292288 but the commit is not in `main` branch.

Do you plan to merge e08bd1292288 into `main` branch? I'd like to avoid having to rebase it [downstream](https://github.com/freebsd/freebsd-ports/commit/d0ada09b16b1): ``` $ git checkout v0.3 && git cherry-pick -x e08bd1292288 Auto-merging dwl.c...

> For the pktinfo types, do those exist on BSDs? Maybe add them in libc upstream? `IP_PKTINFO` exists on [NetBSD](https://github.com/netbsd/src/commit/94b7bfa100ff90e4cc35ff2ddceb2192a6344b7f) but not DragonFly, FreeBSD, OpenBSD. CC @asomers

Also [affects FreeBSD](https://forums.freebsd.org/threads/vulkan-caps-viewer-segmentation-fault.87083/) where the binary package is built with `DEFINES+=X11 WAYLAND`. [Applying](https://github.com/freebsd/freebsd-ports/commit/387f99b7180f) #109 helps but I've skipped qmake changes as auto-detection impedes reproducibility.

Can this be worked around without removing `*.a` static libraries? I'm trying to find a fix for [mepo package](https://www.freshports.org/astro/mepo) that got regressed by zig 0.9.1 -> 0.10.0 update. **EDIT**: found...

[dwlb](https://github.com/kolunmi/dwlb) (mentioned in [the wiki](https://github.com/djpohly/dwl/wiki) since [2023-02-15](https://github.com/djpohly/dwl/wiki/Home/_compare/0223459...44e6f0a)) uses fcft instead of pango.

Given FreeBSD CI is already failing (see below, unrelated to my changes) there's no point to block review/merge on another PR by marking as a draft. Instead this was tested...

The dependency has been merged, so this one can as well.