Age | Commit message (Collapse) | Author | Files | Lines |
|
The versioned binary should be linked to the libGLESv2.so in the same
directory and not to its location in the host build path.
Change-Id: Id8b3a85f9cbde8d67ff1027503b4670b9c546950
Signed-off-by: Damian Hobson-Garcia <dhobsong@igel.co.jp>
|
|
To keep core-image-minimal clean of the 3rdparty components, we
need to add the requirements where they are needed and not
globally in the local.conf.sample - fix this.
Change-Id: I202fd35a5d081f0634a4b22a7f7ad55a80a34260
Signed-off-by: Jan-Simon Möller <jsmoeller@linuxfoundation.org>
|
|
Some popular software, including Chromium/QtWebEngine, look
for a library named "libGLESv2.so.2" on the filesystem to
initialize their OpenGL ES backend :
https://github.com/qtproject/qtwebengine/blob/dev/src/core/
surface_factory_qt.cpp#L83
but the proprietary userspace driver is named "libGLESv2.so"
instead. Let us create a symbolic link which will satisfy
this requirement (we do not rename the binary and make
"libGLESv2.so" a symbolic link, because this would trigger
a Yocto QA warning and prevent building).
Change-Id: Iea901694e90cfd4a786087507cfc77302c9d3b8a
Signed-off-by: Manuel Bachmann <mbc@iot.bzh>
Author: Yannick Gicquel <yannick.gicquel@iot.bzh>
Author: Manuel Bachmann <mbc@iot.bzh>
|
|
The GLES user module has a runtime dependency on the GLES kernel module.
Make that clear by adding an RDEPENDS for it.
|
|
Signed-off-by: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>
|