Closed n3rdopolis closed 3 years ago
That does look like a bug but I cannot reproduce it. What version of which distro are you on?
Debian 11, Wayland master, and my own build CMake v3.20.2
I set up a Debian 11 VM just now and it seems to build a shared library for Wayland just fine there. Could there be something stale in your CMake build directory? What version of the wayland-protocols
package do you have installed?
Hi
Nothing should be stale in there, the scripts I have ensures a clean build. I use a new Wayland-Protocols, but since I was able to build in July, nothing breaking seems to be in there to me.
Wait, dang I think it's commit dffe203c178ecea44a0c3d52a7b62c45a6615944 that's actually the isse, and I can see that the issue is just failing to build some tests and examples, which makes a little more sense?
That does make more sense but I cannot reproduce it. Tried again now with wayland-protocols 1.21 from experimental.
Try with wayland master (not Wayland Protocols), I tried a few commits back, and it built. I think this was also compound with https://gitlab.freedesktop.org/wayland/wayland/-/commit/0e0274af0c9f60d2759713df136f4294054c9096 and the wayland-scanner utility
Please see if the wayland-atomic-marshalling-fix
branch works for you.
Thanks, that worked!
Thank you for reporting and testing!
Commit 71829a0f0de23345fecc7576a0541f6fbec78b25 breaks building glfw with
on Linux, I get a bunch of linker errors