Undefined function 'wl_egl_window_resize'

[Joaquim Duran]

Hello,

> Just curious, what Wayland display server are you going to run Weston with the wayland-backend on?

I expect to run weston in an ARM based device, running on top of
hardware: fbdev, egl, cairo or anyother but no X11 should be involved.
Currently, the device has the fbdev, EGL and GLESv2 drivers.

> Looks like we don't have the #ifdefs to allow building the
wayland-backend without a Wayland-supporting EGL implementation, even
though wayland-backend does support also the Pixman renderer. How did
you get past the requirement of wayland-egl.pc in ./configure?

I've configured bash variables:

export WAYLAND_COMPOSITOR_CFLAGS=$CXXFLAGS
export WAYLAND_COMPOSITOR_LIBS=$LDFLAGS" -lwayland-client -lwayland-cursor"

---

Also, I've compiled drm library with omap driver (this is the only
driver that i need). I don't know if it is an error or not but x86
related file is included in compositor-drm.c:

In file included from src/compositor-drm.c:42:0:
/home/gem-med/Logic_BSPs/Linux_3.0/Linux_BSP/rootfs/usr/include/xf86drm.h:40:17:
fatal error: drm.h: No such file or directory
compilation terminated.
make[1]: *** [src/drm_backend_la-compositor-drm.lo] Error 1
make[1]: Leaving directory `/home/gem-med/Logic_BSPs/Linux_3.0/src/weston'

Joaquim Duran

2015-10-08 15:52 GMT+02:00 Pekka Paalanen <ppaalanen at gmail.com>:
> On Thu, 8 Oct 2015 13:37:40 +0200
> Joaquim Duran <jduran.gm at gmail.com> wrote:
>
>> Hello,
>>
>> When running the weston, the message is shown:
>>
>> [13:27:56.082] Loading module '/usr/lib/weston/wayland-backend.so'
>> [13:27:56.132] Failed to load module:
>> /usr/lib/weston/wayland-backend.so: undefined symbol:
>> wl_egl_window_destroy
>
> Hi,
>
> Prabhu is right, that API is implemented by the same thing that
> implements EGL, even if it's in a different library. It is intimately
> tied to the EGL implementation.
>
> Just curious, what Wayland display server are you going to run Weston
> with the wayland-backend on?
>
> Looks like we don't have the #ifdefs to allow building the
> wayland-backend without a Wayland-supporting EGL implementation, even
> though wayland-backend does support also the Pixman renderer. How did
> you get past the requirement of wayland-egl.pc in ./configure?
>
> I'm guessing you don't actually want the Wayland backend, but you want
> one of the non-nested backends, e.g. DRM or fbdev, so that you don't
> need *another* display server to run Weston on.
>
> Of the backends, only the wayland-backend uses the wayland-egl API, so
> choosing another backend fixes also that.
>
>
> Thanks,
> pq