Created attachment 192393 [details]
The biggest change:
> libwayland-egl is now part of libwayland, and will presumably be removed
from mesa in the not too distant future.
This is good news for us! All ports that depend on libwayland-egl can now enable Wayland by default, independently of what happens in the Mesa port.
(Wayland-EGL *working* still requires building Mesa with the Wayland platform, but only rebuilding Mesa instead of every UI toolkit is significantly easier.)
I'm aware of this patch, will look as time permits.
+me on this. Willing to test when it will be available.
Also related information:
Created attachment 198077 [details]
Update to 1.16.
(In reply to Greg V from comment #3)
this patch does not remove WAYLAND compile option from
the graphics/mesa-libs neither put it into OPTIONS_DEFAULT...
Does it mean that we still need to re-compile graphics/mesa-libs
from ports with WAYLAND enabled in order to use Wayland-related
ports such as Weston?
(In reply to Denis Polygalov from comment #4)
Yes, I mentioned that in the first post here:
> (Wayland-EGL *working* still requires building Mesa with the Wayland platform, > but only rebuilding Mesa instead of every UI toolkit is significantly easier.)
(In reply to Greg V from comment #5)
thanks for the patch and clarification.
I'm aware about the statement in your first post just seems like
I don't understand all the dependencies.
By comparing outputs of 'pkg info mesa-libs' of mesa-libs compiled
with and without WAYLAND option I can see that the only difference
in "Shared Libs provided" section is presence of libwayland-egl.so.1,
meaning that mesa-libs compiled with WAYLAND option set to ON provide
that extra library only.
Lines in your patch such as:
gave me impression that the libwayland-egl.so.1 moved
to graphics/wayland therefore the WAYLAND compile option
can be excluded from mesa-libs but seems like things are
more complicated than I thought...
A commit references this bug:
Date: Mon Oct 15 23:59:28 UTC 2018
New revision: 482189
graphics/wayland: update to 1.16.0
- New libwayland-egl home for consumers as Mesa 18.2 dropped it
Submitted by: Greg V <firstname.lastname@example.org>
Approved by: maintainer timeout (5 months)
A commit references this bug:
Date: Mon Oct 15 23:59:55 UTC 2018
New revision: 482190
graphics/vulkan-loader: enable Wayland surface
- Rebuild ppsspp and rpcs3 to pick up Wayland support for Vulkan
Submitted by: Greg V (maintainer)
Thanks. Landed. I've left out some unrelated bits:
- libwayland-egl in mesa-libs needs @comment until 18.2 to avoid stage-qa warnings
- pkg-plist change in wayland-protocols was breaking build
WAYLAND isn't globally enabled yet, so an exp-run wasn't necessary due to possible false positives (e.g., bug 226408 comment 3, bug 232299). For one, libwayland-egl cannot be accidentally picked up because graphics/wayland isn't pulled as a dependency by default.
(In reply to Denis Polygalov from comment #6)
Yeah, libwayland-egl moved, but Mesa still needs to be built with WAYLAND enabled because that also enables actual Wayland support in libEGL and others
*** Bug 231765 has been marked as a duplicate of this bug. ***