1 2 Previous Next 15 Replies Latest reply on Jul 13, 2017 1:55 AM by FerryT

    Qt5 on Intel Edison


      I've been trying to build a yocto with Qt5 for the intel edison following this guide http://hobby.farit.ru/qt5-gui-intel-edison/ by Farit . I can build succefully the yocto image with Qt5, but when i try to compile the SDK (for the cross compile using qtcreator) with this command :


      cd ~/iot-devkit-yp-poky-edison-20160606/poky/

      source oe-init-build-env ../build_edison/

      bitbake meta-toolchain-qt5


      I get an error about  multiple .bb files:


      ERROR: Multiple .bb files are due to be built which each provide bluez-hcidump (/home/arbol/Descargas/iot-devkit-yp-poky-edison-20160606/build_edison/../poky/meta/recipes-connectivity/bluez/bluez-hcidump_2.5.bb /home/arbol/Descargas/iot-devkit-yp-poky-edison-20160606/build_edison/../poky/meta-intel-iot-devkit/recipes-connectivity/bluez5/bluez5_5.37.bb).

      This usually means one provides something the other doesn't and should.


      Then, i get another error about bluez4:


      ERROR: Task 1580 (/home/arbol/Descargas/iot-devkit-yp-poky-edison-20160606/build_edison/../poky/meta-qt5/recipes-qt/qt5/qtdeclarative_5.3.2.bb, do_configure) failed with exit code '1'

      ERROR: The recipe bluez4 is trying to install files into a shared area when those files already exist. Those files and their manifest location are:


      Matched in manifest-edison-bluez5.packagedata


      Matched in manifest-edison-bluez5.packagedata


      Matched in manifest-edison-bluez5.packagedata

      Please verify which recipe should provide the above files.

      The build has stopped as continuing in this scenario WILL break things, if not now, possibly in the future (we've seen builds fail several months later). If the system knew how to recover from this automatically it would however there are several different scenarios which can result in this and we don't know which one this is. It may be you have switched providers of something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you need to execute the clean task for both recipes and it will resolve this error. It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. Cleaning those recipes should again resolve this error however switching DISTRO_FEATURES on an existing build directory is not supported, you should really clean out tmp and rebuild (reusing sstate should be safe). It could be the overlapping files detected are harmless in which case adding them to SSTATE_DUPWHITELIST may be the correct solution. It could also be your build is including two different conflicting versions of things (e.g. bluez 4 and bluez 5 and the correct solution for that would be to resolve the conflict. If in doubt, please ask on the mailing list, sharing the error and filelist above.


      So, i don't have the toolchain for Qt5 and that means i don't have qmake for the cross compile using qtcreator. Nevertheless i'm available to compile the SDK with the regular command:


      bitbake edison-image -c populate_sdk


      But this one doesn't generate qmake.


      Can you help me please, thank you in advance.

        1 2 Previous Next