[Yocto 1.1.0] Cannot build fsl-image-qt5 twice with different machines

[charleshuang]

Hi FSL,

I find a build problem about fsl-image-qt5.
Here is the reproduce step.

1. Get the Yocto BSP 3.10.53_1.1.0 and set up environment.
   $ EULA=1 MACHINE=imx6qsabresd source fsl-setup-release.sh -b build_all -e x11
  
2. Start building fsl-image-qt5 and it's OK to generate the image this time.
   $ bitbake fsl-image-qt5
  
3. Then, I try to build for my customized machine.
   $ EULA=1 MACHINE=imx6qubcds31 source fsl-setup-release.sh -b build_all -e x11
   $ bitbake fsl-image-qt5

4. However, it will get failure this time. (Please refer to attached log file for details)
   ERROR: Task 1493 (/bsp/sources/meta-qt5/recipes-qt/qt5/qtbase_5.2.1.bb, do_package) failed with exit code '1'

If I build my customized machine first, it can build successfully.

The problem only happens when I build fsl-image-qt5 for another machine after one is complete.

Furthermore, I find the root cause is that some QT related configurations are assigned in class level, e.g. OE_QMAKE_PATH_LIBS.
So, the path relative to specific machine are fixed and it will cause build failure for other machines.

Do you have any idea to fix or avoid this problem?

Thanks,
Daniel

Original Attachment has been moved to: fsl-image-qt5_build_fail.txt.zip

[强王]

Dear  charles:

          i have the same problem, i hope freescale will fix qt

[danielhung]

Hi Qiang,

Here is a stupid method to build successfully. You can do cleansstate for all QT related packages first, before you make image again.

But I think it should be another smarter way to fix it. Look forward for Freescale's update.

bitbake qtbase-native -c cleansstate

bitbake qtbase -c cleansstate

bitbake qtdeclarative -c cleansstate

bitbake qtxmlpatterns -c cleansstate

bitbake qtwayland -c cleansstate

bitbake qtmultimedia -c cleansstate

bitbake qt3d -c cleansstate

bitbake qtgraphicaleffects -c cleansstate

bitbake qt5nmapcarousedemo -c cleansstate

bitbake qt5everywheredemo -c cleansstate

bitbake quitbattery -c cleansstate

bitbake qtsmarthome -c cleansstate

bitbake qtsensors -c cleansstate

bitbake cinematicexperience -c cleansstate

bitbake qt5nmapper -c cleansstate

bitbake quitindicators -c cleansstate

bitbake qtlocation -c cleansstate

bitbake qtwebkit -c cleansstate

bitbake qtwebkit-examples -c cleansstate

Best regards,

Daniel

[jim_lin]

Hello Daniel,

since this the glitch in build-script which will not impact the compiled binary files, manually cleanstate can be the solution for this BSP version, it will not impact the results of the code-building.

Jim Lin.

[gusarambula]

Thanks, Daniel, for the comment. Perhaps this glitch won't happend or will be fixed on the Community BSP as the BSP Release only supports the machines listed on the Release Notes.

[强王]

Dear  charles:

     Thank your guide