FTBS: mixer (eel, 4a)
Description
Environment
Attachments
- 22 Jun 2018, 06:34 AM
relates to
Activity
Loïc Collignon [ IoT.bzh ] June 26, 2018 at 9:31 PM
To answer why cmake and not qmake, here is some hints:
qmake is not widely used, almost only when Qt is used
qmake is used when project is created with QtCreator, you should not assume people will use this IDE.
qmake does not provide support for cmake submodules (controller, helpers, app-templates, ...) which is required now.
qmake has way less features than cmake
QtCreator IDE support cmake projects
Almost all other projects are based on cmake or make
cmake can do everything that qmake can do, even when there is a lot of Qt and Qml
I think all qml project do use qmake just because they were created using QtCreator, which is the easy and fast way to do it, but not the only nor universal way.
Also, I tought that compilation should be done using autobuild scripts (which is the case when built using Jenkins). Those scripts should abstract the real (q|c)?make, therefor inherit from cmake or qmake5 should not be done anymore, right ? Maybe we need a new "autobuild" to inherit from ? In my opinion, whatever the package is, whoever is building it, it should be every time the same method. If Jenkins do it using a method, then we should use this very same method in yocto/bitbake and manually using the SDK.
Stephane Desneux June 26, 2018 at 11:04 AM(edited)
The commit pushed here and merged recently doesn't work: even when 4A is enabled, the wrong SRCREV is taken (that is eel_5.0.3). Maybe it fails because it's not a machine specific but distro-feature specific... Not sure. To be checked in the manual.
Anyway, we have the issue with conditional inherit that can't be solved with a single recipe.
So the solution may be to have 2 recipes, which inherit from different classes and use different revisions.
Then we use a virtual mixer in the packagegroup. That's the cleanest way IMO
Alternatively, we could play with conditional includes which is not better...
Stephane Desneux June 22, 2018 at 6:34 AM
Current WIP recipe attached.
Still an error to be investigated:
CMake Error at afb-helpers/CMakeLists.txt:51 (qt5_use_modules):
Unknown CMake command "qt5_use_modules".
Jan-Simon Moeller June 21, 2018 at 1:48 AM
No. s/qmake5/cmake/ does not Work in the recipe.
ERROR: mixer-1.0+gitAUTOINC+62bb1f0cea-r0 do_configure: Function failed: do_configure (log file is located at /home/scratch/AGL/repobuild-eel/build-rpi3-4a/tmp/work/armv7vehf-neon-vfpv4-agl-linux-gnueabi/mixer/1.0+gitAUTOINC+62bb1f0cea-r0/temp/log.do_configure.10685) ERROR: Logfile of failure stored in: /home/scratch/AGL/repobuild-eel/build-rpi3-4a/tmp/work/armv7vehf-neon-vfpv4-agl-linux-gnueabi/mixer/1.0+gitAUTOINC+62bb1f0cea-r0/temp/log.do_configure.10685 Log data follows: | DEBUG: Executing shell function qmake5_base_preconfigure | DEBUG: Shell function qmake5_base_preconfigure finished | DEBUG: Executing shell function do_configure | ls: cannot access '/home/scratch/AGL/repobuild-eel/build-rpi3-4a/tmp/work/armv7vehf-neon-vfpv4-agl-linux-gnueabi/mixer/1.0+gitAUTOINC+62bb1f0cea-r0/git/*.pro': No such file or directory | WARNING: /home/scratch/AGL/repobuild-eel/build-rpi3-4a/tmp/work/armv7vehf-neon-vfpv4-agl-linux-gnueabi/mixer/1.0+gitAUTOINC+62bb1f0cea-r0/temp/run.do_configure.10685:1 exit 2 from 'PROFILES="`ls /home/scratch/AGL/repobuild-eel/build-rpi3-4a/tmp/work/armv7vehf-neon-vfpv4-agl-linux-gnueabi/mixer/1.0+gitAUTOINC+62bb1f0cea-r0/git/*.pro`"' | ERROR: Function failed: do_configure (log file is located at /home/scratch/AGL/repobuild-eel/build-rpi3-4a/tmp/work/armv7vehf-neon-vfpv4-agl-linux-gnueabi/mixer/1.0+gitAUTOINC+62bb1f0cea-r0/temp/log.do_configure.10685) ERROR: Task (/home/scratch/AGL/repobuild-eel/meta-agl-demo/recipes-demo-hmi/mixer/mixer_git.bb:do_configure) failed with exit code '1' NOTE: Tasks Summary: Attempted 7171 tasks of which 4583 didn't need to be rerun and 1 failed.Summary: 1 task failed: /home/scratch/AGL/repobuild-eel/meta-agl-demo/recipes-demo-hmi/mixer/mixer_git.bb:do_configureWhy is a qml app not using qmake as it should ?!