From: "Naveen Saini" <naveen.kumar.saini@intel.com>
To: Randy Li <ayaka@soulik.info>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2 0/2] meson: fixup nativesdk sysroot
Date: Thu, 31 Dec 2020 04:43:16 +0000 [thread overview]
Message-ID: <390f5f92da9944a08fea5c65b5e04a10@intel.com> (raw)
In-Reply-To: <E4DB717E-1AD6-4B7D-8A6B-91217F3C5769@soulik.info>
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.
+ 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
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: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of Randy Li
> Sent: Thursday, December 31, 2020 9:46 AM
> To: Richard Purdie <richard.purdie@linuxfoundation.org>
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH v2 0/2] meson: fixup nativesdk sysroot
>
>
> > On Dec 30, 2020, at 10:05 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org> 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
next prev parent reply other threads:[~2020-12-31 4:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 3:55 [PATCH v2 0/2] meson: fixup nativesdk sysroot Randy Li
2020-12-29 3:55 ` [PATCH v2 1/2] meson: don't turn sting into a list in nativesdk Randy Li
2020-12-30 23:38 ` [OE-core] " Peter Kjellerstedt
2020-12-31 1:51 ` Randy Li
2020-12-29 3:55 ` [PATCH v2 2/2] meson: add sysroot property Randy Li
2020-12-30 14:05 ` [OE-core] [PATCH v2 0/2] meson: fixup nativesdk sysroot Richard Purdie
2020-12-31 1:46 ` Randy Li
2020-12-31 4:43 ` Naveen Saini [this message]
2020-12-31 6:15 ` Randy Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=390f5f92da9944a08fea5c65b5e04a10@intel.com \
--to=naveen.kumar.saini@intel.com \
--cc=ayaka@soulik.info \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.