It would appear that the more I try with the whole
bitbaking shenanigans, the more issues I come across. I’m determined not to admit defeat but maybe I should just head to the pub instead!
This time though, I don’t think I’m doing anything silly…
So, I’m attempting to bitbake the
angstrom-lxde-image for the
apalis-tk1 and having correctly configured the
local.conf file to specify the
MACHINE ?= "apalis-tk1", I’ve also added the following to ensure that all Qt5 packages are included in the image:
IMAGE_INSTALL_append = " qt3d qt5-plugin-generic-vboxtouch qtbase qtcanvas3d qtcharts qtconnectivity qtdatavis3d qtdeclarative qtenginio qtgraphicaleffects qtimageformats qtlocation qtmultimedia qtquick1 qtquickcontrols2 qtquickcontrols qtscript qtsensors qtserialport qtsvg qtsystems qttools qttranslations qtvirtualkeyboard qtwebchannel qtwebkit-examples qtwebkit qtwebsockets qtxmlpatterns openssh-sftp-server gdb gdbserver "
The bitbake completed successfully, as expected, and I created the SDK and Qt5 toolchain using the
bitbake meta-toolchain-qt5. I installed the SDK successfully into
/usr/local/oecore-x86_64 and set up the environment as explained in a Toradex guide and then proceeded to launch
Now, when trying to build any of the OpenGL examples, the compiler complains that the
GL/gl.h file is not found. I’ve checked that the Qt Kit is configured correctly, with the
sysroots pointing to the right place and this is definitely correct.
My understanding is that
GL/gl.h is part of the
libgles2-mesa-dev, should this not already be one of the recipes used during bitbaking? Also, what with the TK1 supporting OpenGL 4.4 and OpenGLES 3.1, how can these features be enabled out-of-the box (if they aren’t already?).
Thanks (and sorry).