Summary: | [enlightenment overlay] dev-libs/efl-1.8.2 - modules/evas/engines/wayland_egl/evas_wl_main.c:7:1: error: unknown type name 'EGLContext' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dennis Schridde <dschridde+gentoobugs> |
Component: | [OLD] Library | Assignee: | enlightenment+disabled |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://phab.enlightenment.org/T703 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log
build.log |
Description
Dennis Schridde
2013-12-21 00:12:09 UTC
Created attachment 365776 [details]
build.log
Created attachment 365810 [details]
build.log
Similar issue in a 2nd run:
modules/evas/engines/wayland_egl/evas_engine.c: In function 'evgl_symbols':
modules/evas/engines/wayland_egl/evas_engine.c:170:8: error: 'glsym_eglGetProcAddress' undeclared (first use in this function)
if (glsym_eglGetProcAddress) { \
^
Grepping for GL_GLES (which guards the definition of glsym_eglGetProcAddress in src/modules/evas/engines/wayland_egl/evas_engine.c) shows that it is only defined in ./m4/evas_check_engine.m4 within the macro EVAS_CHECK_ENGINE_DEP_GL_XLIB. So I assume that EGL and thus Wayland support needs to depend on USE=X.
As you already noticed, the situation is more complex and just enabling USE=X wont fix the build failures. Since i dont use/play with wayland, while you already did some debugging in the edevelop irc channel, please continue checking with upstream for bugfixes/workarounds and report back. The problem is this line in the ebuild: REQUIRED_USE="wayland? ( egl || ( opengl gles ) )" Combined with this part: use opengl && use gles && { einfo "You enabled both USE=opengl and USE=gles, but only one can be used" einfo "opengl has been selected for you" } Wayland support apparently requires GLES support. While this requirement is potentially an overlooked corner case inside EFL (whose source code and #ifdefs generally suggests that OpenGL should work as well), the current state needs to be reflected by a different REQUIRED_USE="wayland? ( egl gles )" In addition, this requires REQUIRED_USE=" opengl? ( !gles ) gles? ( !opengl ) " and the autoselection mentioned above to be removed. I figured this out by setting USE=+wayland,+gles,-opengl (beware of bug #496256!). Upstream bugreport: https://phab.enlightenment.org/T703 (E's Phabricator is not allowed for See-Also, thus I linked it as URL instead) (In reply to Dennis Schridde from comment #4) > Wayland support apparently requires GLES support. raster just confirmed this (https://phab.enlightenment.org/T703#6): > this is by design in the code. egl is bound to glesv2 by design in the code. until wayland started pushing the idea of desktop gl with egl , egl was bound to gles1/2 and never used/seen anywhere else, thus the gl code is built this way. thanks for your report and your work invested to find out the specific details, the ebuild in the overlay has now been updated. Please open a new bug when upstream fixes the usage with opengl. |