Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. QT_FEATURE_opengles32 in meta-toolchain-qt6 for iMX6DL

QT_FEATURE_opengles32 in meta-toolchain-qt6 for iMX6DL

Scheduled Pinned Locked Moved Unsolved Mobile and Embedded
1 Posts 1 Posters 32 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    ATSam
    wrote last edited by ATSam
    #1

    I'm trying to build a cross-compilation toolchain for an iMX6DL.
    I've managed to produce a toolchain from the meta-toolchain-qt6 recipe but compiling against this toolchain is failing because it attempts to find an OpenGL3.2 header.
    The iMX6DL does not support OpenGL3.2 (only 2.0) so it is correct that the toolchain does not contain this header, but Qt also shouldn't be looking for it.

    Ultimately it seems that the problem is the QT_FEATURE_opengles32 define is set to 1 in qtgui-config.h in the target sysroot.
    If I set this to -1 (and the same with QT_FEATURE_opengles31 and QT_FEATURE_opengles3) then I can compile successfully, but manually editing the toolchain doesn't seem like the right fix. I'd like to adjust my Yocto configuration so this isn't necessary.

    My Yocto PACKAGECONFIG contains "eglfs opengles2" and does not contain "opengl", which seems correct.
    The toolchain contains EGL/ and GLES2/ directories (no GLES3) in the target sysroot
    Output from the QtBase configure step shows:
    -DFEATURE_opengl_desktop=OFF -DFEATURE_opengles2=ON -DFEATURE_eglfs=ON -DFEATURE_eglfs_egldevice=OFF

    Although it also shows:
    CMake Warning:
    Manually-specified variables were not used by the project:

    ...
    FEATURE_eglfs
    FEATURE_eglfs_egldevice
    ...
    FEATURE_opengl_desktop
    FEATURE_opengles2

    So perhaps those flags are not the mechanism that ultimately sets the QT_FEATURE defines?

    Can anyone suggest why the opengles32 feature flag is set and how I should prevent it being set in the first place?

    1 Reply Last reply
    0

    • Login

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Get Qt Extensions
    • Unsolved