gstreamer plugin bbappends on scarthgap-dev branch break gstreamer clients

[g-scott-murray]

Even after commit 5bb1f62 on scarthgap-dev the meta-rcar-gen3 gstreamer plugin bbappends break gstreamer clients. They build the Renesas 1.20.3 forked versions and package them with the 1.22 version number, which does build, but the resulting mismatch between them and the header files from the actual gstreamer 1.22 package results in build failures of gstreamer using code (e.g. our camera-gstreamer application in AGL). The bbappends should either be:

• removed until Renesas is able to actually rebase the fork(s) to 1.22.x
• renamed back to 1.20.3 and you can add a forward port of the main gstreamer 1.20.3 recipe (and probably gstreamer-plugins-ugly) to meta-rcar-gen3, and users can set PREFERRED_VERSION to force using them if desired.

[harunobukurokawa]

Thank you for the report. let me check..

[DuyDang007]

Hi @g-scott-murray ,

We fixed it by porting the full gstreamer recipes, not using bbappend anymore.

Could you check this again?

Best Regards,
Duy Dang

[g-scott-murray]

On Tue, Aug 13, 2024 at 2:35 AM DuyDang ***@***.***> wrote: Hi @g-scott-murray <https://github.com/g-scott-murray> , We fixed it by porting the full gstreamer recipes, not using bbappend anymore. Could you check this again?

Okay, I will try using the HEAD of scarthgap-dev in a test build. Nothing needs to be done other than having "multimedia" in MACHINE_FEATURES, is that correct? Thanks, Scott Message ID: ***@***.***>

…

[DuyDang007]

Okay, I will try using the HEAD of scarthgap-dev in a test build. Nothing needs to be done other than having "multimedia" in MACHINE_FEATURES, is that correct? Thanks, Scott Message ID: @.***>
…

Yes. It is correct.