...
Currently RDK OSS does by default opposite of what wayland graphics guys tried to achieve with libwayland-egl.so split. RDK removes the 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 Should be changed once all SoC SoCs support this split modegeneric 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)
...
Since However since library is only provided as a prebuild binary and not as source (access 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) we and as long as RDK-M cannot investigate and 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
...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
"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 in RDK6 no issue(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
...