vspmif-user-module, qosif-user-module: fix header installation

[fredcadete]

The recipe is installing headers directly to the sysroot and so they are not tracked in sstate. This causes sporadic problems in builds that reuse sstate.

To reproduce the proble,:

• normal setup
• bitbake vspmif-tp-user-module
• mv tmp tmp-old (simulates reusing only sstate)
• bitbake vspmif-tp-user-module -c cleansstate
• bitbake vspmif-tp-user-module

[fredcadete]

The same issue happened with qosif-user-module

[tasaito]

Hi Frederico-san,

Thank you for your report.

About this problem, investigation is started in our Team. It will be improved by the next release.

Regards,

[tasaito]

Hi Frederico-san,

The same problem occurs also in Renesas-Yocto-v2.12.0.

The shared include file is installed in /usr/local/include by do_install. However, ${STAGING_INCDIR} is /usr/include. Therefore, SSTATE can not recreate /usr/local/include.

STAGING_INCDIR = "${STAGING_DIR_HOST}/${includedir}" We have to change "/usr/include" into "/usr/local/include".

W/A sample is the following. qosif is also the same. [vspm-user-module.bb]

--- a/meta-rcar-gen3/recipes-multimedia/vspmif-module/vspmif-user-module.bb
+++ b/meta-rcar-gen3/recipes-multimedia/vspmif-module/vspmif-user-module.bb
@@ -11,6 +11,9 @@ VSPMIF_LIB_DIR = "vspm_if-module/files/vspm_if"

 EXTRA_OEMAKE = "ARCH=${TARGET_ARCH}"

+includedir = "/usr/local/include"
+SSTATE_DUPWHITELIST = "${STAGING_INCDIR}"
+
 do_compile() {
     export VSPM_LEGACY_IF="1"

We will fix this problem in the next release.

Regards, Takeshi Saito