dev-libs/ecore and media-libs/evas currently have no wayland useflags and thus wayland support is enabled automagically. For ecore, this results in: Optional Modules: Ecore Evas: Ecore_Evas...................: yes Wayland Shm................: no Wayland Egl................: no While for evas the wayland engine is enabled, but would never run: Engines: Wayland Shm................: yes Wayland Egl................: yes This was pointed out to me on Freenode at #edevelop
Further, it needs REQUIRED_USE="wayland? ( gles )", otherwise you will get the following error when compiling evas: evas_wl_main.c: In function 'eng_window_new': evas_wl_main.c:197:18: error: 'Evas_Engine_GL_Context' has no member named 'egldisp'
And since there is currently no way to disable wayland support, this creates a problem. So at the very least we need a --disable-wayland in these ebuilds.
(In reply to comment #2) > And since there is currently no way to disable wayland support, this creates > a problem. So at the very least we need a --disable-wayland in these ebuilds. The flags are actually named differently, and the dependency on gles needs to be respected, so this makes it: $(use gles && use_enable wayland wayland-egl) $(use_enable wayland wayland-shm)
This should be fixed in evas-1.7.5-r1 and ecore-1.7.5-r1. Please test and report back.
(In reply to comment #4) > This should be fixed in evas-1.7.5-r1 and ecore-1.7.5-r1. Please test and > report back. I tested USE="+wayland -gles" and it builds and runs. I did not test actual wayland support, though, because there is no display manager available in portage, yet.
