To update the wlroots subproject use
meson subprojects update wlroots
Chases wlroots 68c8cef38edafa5e52532e0b43a4888554168361
cursor: Don't warp to (0,0) when last output is disconnected
Fixes#561
To update the wlroots subproject use
meson subprojects update wlroots
Chases wlroots fa7d2cb8d60ed48c44c707106c03682056ddfaca
wlr_scene: Only consider visible parts of the node when culling background
Fixes#501
To update the wlroots subproject use
meson subprojects update wlroots
Chases wlroots 91943a68a6976ef7c4cc70afc07954a00fae678b
wlr_input_device: remove anon union field
Fixes#415
As it turns out the reason for the workaround was a bug
in wlroots which got fixed in the meantime.
So to keep things simple just revert the workaround and
depend on the wlroots fix instead.
To update the wlroots subproject use
meson subprojects update wlroots
This reverts commit e87aa19066.
Make the subproject wrap file declare the dependencies it provides.
Remove the manual subproject invocation and allow Meson to select
whichever wlroots it finds which satisfies the version requirement --
either a system one via pkg-config, or the subproject fallback.
Use a dependency-generic method of acquiring wlroots configuration info
-- enabled features are present in the pkg-config file and additionally
exported as declare_dependency() variables, so there is no need to do C
preprocessor checks for it.
This ensures that Meson best practices are followed, and also...
Fixes#318
This is better than `revision = master` because:
- It enables labwc commits to be checked out and build without manually
having to find the right wlroots commit to build with
- The labwc master is always buildable without user intervention even
if there are breaking changes in the wlroots master branch
Suggested in issue #289
This simplifies building as there's no need to manually
git clone subprojects anymore.
Building is now as simple as:
meson build
ninja -C build
In order to update the subprojects, meson provides:
meson subprojects update
