This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SK-TDA4VM: Upgrade from QT5 to QT6

Part Number: SK-TDA4VM

Hi,

We are currently using Yocto Linux 09.01 which comes with meta-qt5 layer. We wish to upgrade to meta-qt6 for running QT application which have been developed using QT6. We had replaced the meta-qt5 layer with meta-qt6 and updated bblayers.

While building qtcore recipe (bitbake -k qtcore) we are facing issues where it is not able to find qtcore-conf-native.

Can you please let us know if there is any process to upgrade 09.01 from QT5 to QT6 or will there be a release from TI with QT6.

Thanks,

Soumya

  • Hi Soumya,

    Can you send the entire error log so I can see more details?

    Best,
    Jared

  • At first, we copied meta-qt6 inside the sources folder and changed the bblayer file to include meta-qt6 and removed meta-qt5. After that we executed the following command and it gave this error:

    HP-280-G4-MT-Business-PC:~/ti-yocto/build$ BB_NUMBER_THREADS='3' PARALLEL_MAKE='-j 3' bitbake -k qtbase
    WARNING: Duplicate inclusion for /home/developer/ti-yocto/sources/meta-arago/meta-arago-distro/conf/distro/include/branding-core.inc in /home/developer/ti-yocto/sources/meta-arago/meta-arago-distro/conf/distro/arago.conf
    WARNING: Duplicate inclusion for /home/developer/ti-yocto/sources/meta-arago/meta-arago-distro/conf/distro/include/branding-core.inc in /home/developer/ti-yocto/sources/meta-arago/meta-arago-distro/conf/distro/arago.conf
    NOTE: Started PRServer with DBfile: /home/developer/ti-yocto/build/cache/prserv.sqlite3, Address: 127.0.0.1:39047, PID: 83329
    ERROR: Layer 'meta-arago-distro' depends on layer 'qt5-layer', but this layer is not enabled in your configuration
    ERROR: Layer 'meta-arago-demos' depends on layer 'qt5-layer', but this layer is not enabled in your configuration

    We then modified the layer.conf file specified in the path from qt5-layer to qt6-layer. Once that was done we executed the same command again.

    HP-280-G4-MT-Business-PC:~/ti-yocto/build$ BB_NUMBER_THREADS='3' PARALLEL_MAKE='-j 3' bitbake -k qtbase
    WARNING: Duplicate inclusion for /home/developer/ti-yocto/sources/meta-arago/meta-arago-distro/conf/distro/include/branding-core.inc in /home/developer/ti-yocto/sources/meta-arago/meta-arago-distro/conf/distro/arago.conf
    WARNING: Duplicate inclusion for /home/developer/ti-yocto/sources/meta-arago/meta-arago-distro/conf/distro/include/branding-core.inc in /home/developer/ti-yocto/sources/meta-arago/meta-arago-distro/conf/distro/arago.conf
    NOTE: Started PRServer with DBfile: /home/developer/ti-yocto/build/cache/prserv.sqlite3, Address: 127.0.0.1:38713, PID: 83805
    Loading cache: 100% |                                                                                                                                                                              | ETA:  --:--:--
    Loaded 0 entries from dependency cache.
    ERROR: ParseError at /home/developer/ti-yocto/sources/meta-arago/meta-arago-demos/classes/qt5.bbclass:6: Could not inherit file classes/qmake5.bbclass                                                    | ETA:  0:01:27
    ERROR: Parsing halted due to errors, see error messages above
    
    Summary: There were 2 WARNING messages.
    Summary: There were 2 ERROR messages, returning a non-zero exit code.

    As meta-arago-demos was giving build error after this, we removed it from the bblayers. ti-apps-launcher and edgeai-gui-app has also been removed as it was giving the error. Again we executed the command to build qtcore.

    HP-280-G4-MT-Business-PC:~/ti-yocto/build$ BB_NUMBER_THREADS='3' PARALLEL_MAKE='-j 3' bitbake -k qtbase
    WARNING: Duplicate inclusion for /home/developer/ti-yocto/sources/meta-arago/meta-arago-distro/conf/distro/include/branding-core.inc in /home/developer/ti-yocto/sources/meta-arago/meta-arago-distro/conf/distro/arago.conf
    WARNING: Duplicate inclusion for /home/developer/ti-yocto/sources/meta-arago/meta-arago-distro/conf/distro/include/branding-core.inc in /home/developer/ti-yocto/sources/meta-arago/meta-arago-distro/conf/distro/arago.conf
    NOTE: Started PRServer with DBfile: /home/developer/ti-yocto/build/cache/prserv.sqlite3, Address: 127.0.0.1:36927, PID: 83939
    Loading cache: 100% |###############################################################################################################################################################################| Time: 0:00:01
    Loaded 5989 entries from dependency cache.
    Parsing recipes: 100% |#############################################################################################################################################################################| Time: 0:00:32
    Parsing of 6144 .bb files complete (3958 cached, 2186 parsed). 9270 targets, 592 skipped, 0 masked, 0 errors.
    WARNING: No recipes in default available for:
      /home/developer/ti-yocto/sources/meta-arago/meta-arago-distro/recipes-qt/qt5/qtwebkit_%.bbappend
    No recipes in k3r5 available for:
      /home/developer/ti-yocto/sources/meta-arago/meta-arago-distro/recipes-qt/qt5/qtwebkit_%.bbappend
    NOTE: Resolving any missing task queue dependencies
    ERROR: Nothing RPROVIDES 'qtbase-conf-native' (but virtual:native:/home/developer/ti-yocto/sources/meta-qt6/recipes-qt/qt6/qtbase_git.bb RDEPENDS on or otherwise requires it)
    NOTE: Runtime target 'qtbase-conf-native' is unbuildable, removing...
    Missing or unbuildable dependency chain was: ['qtbase-conf-native']
    NOTE: Runtime target 'qtbase-qmlplugins' is unbuildable, removing...
    Missing or unbuildable dependency chain was: ['qtbase-qmlplugins', 'qtbase-native', 'qtbase-conf-native']
    NOTE: Runtime target 'qtbase-plugins' is unbuildable, removing...
    Missing or unbuildable dependency chain was: ['qtbase-plugins', 'qtbase-native', 'qtbase-conf-native']
    NOTE: Runtime target 'qtbase-staticdev' is unbuildable, removing...
    Missing or unbuildable dependency chain was: ['qtbase-staticdev', 'qtbase-native', 'qtbase-conf-native']
    NOTE: Runtime target 'qtbase' is unbuildable, removing...
    Missing or unbuildable dependency chain was: ['qtbase', 'qtbase-native', 'qtbase-conf-native']
    NOTE: Runtime target 'qtbase-dev' is unbuildable, removing...
    Missing or unbuildable dependency chain was: ['qtbase-dev', 'qtbase-native', 'qtbase-conf-native']
    NOTE: Resolving any missing task queue dependencies
    NOTE: Resolving any missing task queue dependencies
    NOTE: Resolving any missing task queue dependencies
    
    Build Configuration (mc:default):
    BB_VERSION           = "2.0.0"
    BUILD_SYS            = "x86_64-linux"
    NATIVELSBSTRING      = "ubuntu-22.04"
    TARGET_SYS           = "aarch64-oe-linux"
    MACHINE              = "j721e-evm"
    DISTRO               = "arago"
    DISTRO_VERSION       = "2023.10"
    TUNE_FEATURES        = "aarch64"
    TARGET_FPU           = ""
    meta-arago-distro    
    meta-arago-extras    
    meta-arago-test      = "HEAD:190e2b58fb6c1e3c658fe2f7afc40a2863007bbc"
    meta-qt6             = "dev:97ae6a24870cd2434581c313e6925279d72fa91a"
    meta-virtualization  = "HEAD:67b0ef4256a484851f3556d281ca4caa88374388"
    meta-networking      
    meta-python          
    meta-oe              
    meta-gnome           
    meta-filesystems     = "HEAD:402affcc073db39f782c1ebfd718edd5f11eed4c"
    meta-ti-extras       
    meta-ti-bsp          = "HEAD:6ad91a192fa1ab33775a22894a413aefd0b67106"
    meta-arm             
    meta-arm-toolchain   = "HEAD:b187fb9232ca0a6b5f8f90b4715958546fc41d73"
    meta                 = "HEAD:b77cd331199fa62e3b162f37efca3b927c68d8e5"
    meta-tisdk           = "HEAD:d0a92bc0a53276a3faad16ed52084451f4d1b3bf"
    meta-edgeai          = "HEAD:02ce7e60b449c72def00f26afc549034cbd82ba9"
    
    
    Build Configuration:
    BB_VERSION           = "2.0.0"
    BUILD_SYS            = "x86_64-linux"
    NATIVELSBSTRING      = "ubuntu-22.04"
    TARGET_SYS           = "arm-oe-eabi"
    MACHINE              = "j721e-evm-k3r5"
    DISTRO               = "arago"
    DISTRO_VERSION       = "2023.10"
    TUNE_FEATURES        = "arm armv7a vfp thumb callconvention-hard"
    TARGET_FPU           = "hard"
    meta-arago-distro    
    meta-arago-extras    
    meta-arago-test      = "HEAD:190e2b58fb6c1e3c658fe2f7afc40a2863007bbc"
    meta-qt6             = "dev:97ae6a24870cd2434581c313e6925279d72fa91a"
    meta-virtualization  = "HEAD:67b0ef4256a484851f3556d281ca4caa88374388"
    meta-networking      
    meta-python          
    meta-oe              
    meta-gnome           
    meta-filesystems     = "HEAD:402affcc073db39f782c1ebfd718edd5f11eed4c"
    meta-ti-extras       
    meta-ti-bsp          = "HEAD:6ad91a192fa1ab33775a22894a413aefd0b67106"
    meta-arm             
    meta-arm-toolchain   = "HEAD:b187fb9232ca0a6b5f8f90b4715958546fc41d73"
    meta                 = "HEAD:b77cd331199fa62e3b162f37efca3b927c68d8e5"
    meta-tisdk           = "HEAD:d0a92bc0a53276a3faad16ed52084451f4d1b3bf"
    meta-edgeai          = "HEAD:02ce7e60b449c72def00f26afc549034cbd82ba9"
    
    ERROR: All buildable tasks have been run but the build is incomplete (--continue mode). Errors for the tasks that failed will have been printed above.                                              | ETA:  0:00:00
    ERROR: Command execution failed: 1
    
    Summary: There were 3 WARNING messages.
    Summary: There were 3 ERROR messages, returning a non-zero exit code.

    We are not sure as to how can resolve this error.

    ERROR: Nothing RPROVIDES 'qtbase-conf-native' (but virtual:native:/home/developer/ti-yocto/sources/meta-qt6/recipes-qt/qt6/qtbase_git.bb RDEPENDS on or otherwise requires it)

  • Hi Soumya,

    We don't currently support Qt6 in the Arago distribution. There are also no plans for supporting Qt6 in the immediate upcoming SDK releases due to the differences in the licensing between Qt6 and Qt5.

    It appears that the qtbase_git.bb recipe is asking for the qtbase-conf-native recipe, so you may have some luck asking Qt themselves, or the developers of the meta-qt6 layer.

    Best,
    Jared