libwayland-egl.so is the 'Frontend wayland-egl library' that wayland-egl client applications need to link against.
This is a generic library (as of wayland v1.13) that is provided by wayland project and SHOULD NOT be a platform/SoC specific library provided by (SoC) vendor layer .
On some SoCs (Amlogic and Realtek?) the libwayland-egl.so in RDKv6/7 is library provided by SoC vendor layer instead generic frontend lib provided by wayland and we need to fix/resolve that in RDK-8
The wayland graphics experts split wayland-egl between a generic wayland-egl.so frontend library for use by wayland-client applications and versioned backend "wayland-egl-backend-h which serves only as interface, not as library, header file that EGL graphics driver implementations can use"
This was designed to separate this wayland-egl library and applications using it from platform/soc specific EGL drivers, to NOT drag in a platform/soc specific link dependency chain into this library and applications/application containers using it.
The wayland-egl-backend.h is NOT part of the public API for application developers and application do not link to it. It is a versioned interface, helper API that EGL graphics drivers can use.
That split happened in wayland version 1.13. RDK-8 uses kirkstone which uses wayland version 1.20.
More details on reasons and history of this split are described in "History and reasons for split" section.
Here is the wayland source snippet that defines the package config wayland-egl.pc and wayland-egl-backend.pc
wayland-egl.pc leads to the wayland-egl.so library. Note that wayland-egl-backend.pc does NOT provide .so library, it only serves as header, interface for EGL implementation
pkgconfig.generate( name: 'wayland-egl', description: 'Frontend wayland-egl library', version: '18.1.0', requires: 'wayland-client', libraries: wayland_egl ) pkgconfig.generate( name: 'wayland-egl-backend', description: 'Backend wayland-egl interface', version: '3' ) |
On some SoCs (Amlogic and Realtek?) the libwayland-egl.so in RDKv6/7 is library provided by SoC vendor layer instead generic frontend lib provided by wayland and we need to fix/resolve that in RDK-8
Currently RDK OSS does by default opposite of what wayland graphics guys tried to achieve with libwayland-egl.so split. RDK removes the generic libwayland-egl.so provided by Wayland because it expects it to be provided by platform-specific integration. (unless you explicitly use wayland-default-egl.bb recipe) . Should be changed once all SoCs support this generic libwayland-egl.so model
This is current bitbake recipe used in current AH212 version as provider of virtual/libgles but also as RPROVIDES:${PN} += "libwayland-egl.so" , see (access rights are restricted to aml licensees)
currently SRCREV ?= "${SRCREV_AML_BSP}" refers to "AML_BSP_REL_VERSION_RDK6.1.6"
and hence the precompiled so binary that provides libwayland-egl.so is following
However since library is only provided as a prebuild binary and not in source code we cannot see how build recipes work and possibly bring in wrong linking, dependencies and we as RDK-M cannot investigate (access to full source code from Mali requires ARM approval according to Mali DDK license) and as long as RDK-M does not have that arm approval action is fully on amlogic. However Amlogic no longer providing support at the moment! We are stuck.
Info from ARM site : To build a functional OpenGL ES you need access to the full source code of the Mali GPU DDK, which is provided under the standard Arm commercial license to all Mali GPU customers.
https://developer.arm.com/downloads/-/Bifrost%20Mali%203rd%20Gen%20GPU%20Architecture
TO DO insert REFERENCE TO AML Jira TICKET TO INVESTIGATE / FIX this
readelf -d libMali.so | grep NEEDED is https://github.com/stagingrdkm/lgpub/blob/master/dac/templates/oe_4.0/ah212_libs.json#L4899-L4912
"deps": [
"/lib/ld-linux-armhf.so.3",
"/lib/libc.so.6",
"/lib/libdl.so.2",
"/lib/libgcc_s.so.1",
"/lib/libm.so.6",
"/lib/libpthread.so.0",
"/lib/librt.so.1",
"/usr/lib/libdrm.so.2",
"/usr/lib/libstdc++.so.6",
"/usr/lib/libwayland-client.so.0",
"/usr/lib/libwayland-server.so.0"
],
"name": "/usr/lib/libMali.so" |
on broadcom it is ok since move to newer brcm wayland backend (WLPL) in RDK6
libs deps https://github.com/stagingrdkm/lgpub/blob/master/dac/templates/oe_4.0/72126ott_libs.json
issue to be described
Same problem as amlogic
Since library is only provided as prebuild binary and as source code we cannot see how build recipes work and possibly bring in wrong linking, dependencies and we as RDK-M cannot investigate.
libs deps https://github.com/stagingrdkm/lgpub/blob/master/dac/templates/oe_4.0/rtd1319_libs.json
distribution and base layer for firebolt native runtimes and apps
libwayland-egl.so should become part of base-layer. It is currently provided by wayland recipe but it is currently not installed in base-layer rootfs because it is removed as part of following post rootfs image handling https://github.com/rdkcentral/meta-bolt-distro/blob/3c368153f4edb8bf8ae8c95fcec5c3ed995fcacc/meta-bolt-base/classes/base-bolt-image.bbclass#L40
The reason why it is still being removed because when testing we see application is not visible on Amlogic AH212 when using the libwayland-egl.so from wayland in Application container while it works when bind mounting libMali.so as libwayland-egl.so provider. (see Amlogic issue) so when that is fixed we can move to that
see also some of historical wayland discussion threads on this subject, like
Before this split:
After the split: