Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
The migration is almost done, at least the rest should happen in the background. There are still a few technical difference between the old cluster and the new ones, and they are summarized in this issue. Please pay attention to the TL:DR at the end of the comment.
Mesa has had Vulkan support for many years now, and so far no Vulkan demos! This needs to change!
So here's a Vulkan port of the gears demo, with a bunch of limitations:
I think the biggest question mark here is if doing manual WSI like I've done for Wayland here is a good idea in the first place. I was kinda following glxgears precedence here, but I'm not sure it's the right thing to do. I could imagine using either SDL or GLFW here would make things a bit easier to maintain... but it'd also pull in some non-trivial dependencies.
I don't really want to create sepatate vkgears_wayland
/ vkgears_x11
binaries like we do for es2gears
, that just seems messy to me. If so, it's be better to do similar to vkcube does, and either pick API automatically, or explicitly based on a command line switch.
Thoughts?
This MR contains a few patches from !92 (merged). Please review those in that MR, because I want to land that one first.