> On Dec 31, 2020, at 12:43 PM, Saini, Naveen Kumar
> <[email protected]> wrote:
>
> This failing in case of non-native sdk too, where PKG_CONFIG_SYSROOT_DIR is
> also exported. It does not prepend PKG_CONFIG_SYSROOT_DIR path.
>
> I think it should be fixed manually by prepending sysroot path.
I was having such plan but Gstreamer people said it should be fixed in OE itself
https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/merge_requests/1253
>
> + pkgconf_sysroot = run_command(python3, '-c', 'import os;
> print(os.environ.get("PKG_CONFIG_SYSROOT_DIR"))').stdout().strip()
> mfx_incdir = mfx_dep.get_pkgconfig_variable('includedir')
> + mfx_incdir = pkgconf_sysroot + mfx_incdir
>
Sorry, I don’t what the non-native sdk means here, since
get_pkgconfig_variable('includedir') from meson would apply the pkgconfig
sysroot setting from the meson, it would be fine.
>
> Ref:
> https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad/0004-opencv-resolve-missing-opencv-data-dir-in-yocto-buil.patch#n26
>
>
>> -----Original Message-----
>> From: [email protected] <openembedded-
>> [email protected]> On Behalf Of Randy Li
>> Sent: Thursday, December 31, 2020 9:46 AM
>> To: Richard Purdie <[email protected]>
>> Cc: [email protected]
>> Subject: Re: [OE-core] [PATCH v2 0/2] meson: fixup nativesdk sysroot
>>
>>
>>> On Dec 30, 2020, at 10:05 PM, Richard Purdie
>> <[email protected]> wrote:
>>>
>>>> On Tue, 2020-12-29 at 11:55 +0800, Randy Li wrote:
>>>> I still saw the request for this patch from Gstreamer users
>>>> sometimes. I have verified this version would work fine.
>>>>
>>>> Only the exported SDK would need this patch.
>>>
>>> Thanks for the patches, is there something we should add to the
>>> automated tests (e.g. in meta/lib/oeqa/sdk/cases) to test this?
>>>
>> The original case is that when I was compiling the Gstreamer plugins bad for
>> Intel Media SDK, the include path from the pkg-config would be one without
>> sysroot. Most of packages won’t meet such problem, they can just ordinary
>> includedir, which is not from meson but compiler I think, then prepend a
>> package name when its code include thems.
>>
>> I think this case only fix those package using meson and need to get
>> something likes path information from the pkg-config.
>>
>> I have not read the QA part, so I don’t know what is necessary for such case.
>> Maybe a check for the environment variables from all those auto build tools ?
>> I need to read and make the right comment as well as I welcome the idea
>> from the others.
>>> Cheers,
>>>
>>> Richard
>>>
>> Sincerely
>> Randy
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#146321):
https://lists.openembedded.org/g/openembedded-core/message/146321
Mute This Topic: https://lists.openembedded.org/mt/79284744/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
