Inconsistent OpenGL support across architectures
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
qtbase-opensource-src (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Hello,
today I noticed build failures of v4l-utils on arm64 hosts:
https:/
This is due to the OpenGLES2 feature is enabled on arm64 (but this feature is not enabled for amd64):
> /usr/include/
> #define QT_FEATURE_
> #define QT_FEATURE_opengl 1
> #define QT_FEATURE_
> #define QT_FEATURE_
vs:
> /usr/include/
> #define QT_FEATURE_
> #define QT_OPENGL_ES true
> #define QT_OPENGL_ES_2 true
> #define QT_FEATURE_opengl 1
> #define QT_FEATURE_
> #define QT_OPENGL_ES_3 true
> #define QT_FEATURE_
> #define QT_OPENGL_ES_3_1 true
Is the inconsistent feature setting intentional? The Debian Qt packages seem to select Desktop OpenGL across architectures.
Thanks,
Gregor
I guess this is due to the following lines in debian/rules:
gles2_architectures := armel armhf arm64 HOST_ARCH) ,$(findstring $(DEB_HOST_ARCH), $(gles2_ architectures) )) configure_ opts += -opengl es2 configure_ opts += -opengl desktop
ifeq ($(DEB_
extra_
else
extra_
endif
Still my question is why those architectures (should) differ from the regular ones. And why Ubuntu is behaving differently than Debian.
In my case I need access to qopenglext.h contents which does not get loaded if OpenGL ES2 support is present.