build: subproject support for wayland-protocols #6497
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As in wlroots: [1] [1]: swaywm/wlroots#2953
emersion
approved these changes
Sep 8, 2021
|
Thanks! |
|
About the second problem, I realized that there is no point to not require the same version of wayland-protocols that wlroots needs, so I opened #6498. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As in wlroots: swaywm/wlroots#2953.
To build sway on my system with outdated wayland-protocols (1.20):
meson setup --force-fallback-for wayland-protocols buildWithout the force-fallback, sway finds wayland-protocols from the system, which does not satisfy wlroots (>=1.21) and the setup fails without a good error message.
I'll add a note in the wiki if this is merged.