From: "Alexander Kanavin" <alex.kanavin@gmail.com>
To: ayaka <ayaka@soulik.info>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] meson: add sysroot property
Date: Wed, 30 Sep 2020 18:40:12 +0200 [thread overview]
Message-ID: <CANNYZj85ymSHGvm5E7Axtrs6B6-V4nQGCFzcCVJKCM0=wsPtkg@mail.gmail.com> (raw)
In-Reply-To: <20200930150545.3882859-1-ayaka@soulik.info>
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
Wait, how does it work in native meson then?
Alex
On Wed 30. Sep 2020 at 17.06, ayaka <ayaka@soulik.info> wrote:
> I know the environment setup script would set PKG_CONFIG_PATH,
>
> but the meson won't take that env when translate the includedir
>
> property from the pkg-config.
>
>
>
> Signed-off-by: ayaka <ayaka@soulik.info>
>
> ---
>
> meta/recipes-devtools/meson/nativesdk-meson_0.55.1.bb | 1 +
>
> 1 file changed, 1 insertion(+)
>
>
>
> diff --git a/meta/recipes-devtools/meson/nativesdk-meson_0.55.1.bb
> b/meta/recipes-devtools/meson/nativesdk-meson_0.55.1.bb
>
> index 67add2c25e..7fdc4c86d9 100644
>
> --- a/meta/recipes-devtools/meson/nativesdk-meson_0.55.1.bb
>
> +++ b/meta/recipes-devtools/meson/nativesdk-meson_0.55.1.bb
>
> @@ -40,6 +40,7 @@ c_args = @CFLAGS
>
> c_link_args = @LDFLAGS
>
> cpp_args = @CPPFLAGS
>
> cpp_link_args = @LDFLAGS
>
> +sys_root = @OECORE_TARGET_SYSROOT
>
>
>
> [host_machine]
>
> system = '${SDK_OS}'
>
> --
>
> 2.25.4
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 1911 bytes --]
next prev parent reply other threads:[~2020-09-30 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 15:05 [PATCH] meson: add sysroot property Randy Li
2020-09-30 16:40 ` Alexander Kanavin [this message]
2020-10-01 4:14 ` Randy Li
2020-10-01 9:21 ` Alexander Kanavin
2020-10-01 20:38 ` [OE-core] " Khem Raj
2020-10-10 19:43 ` Randy Li
2020-10-01 4:33 ` Khem Raj
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='CANNYZj85ymSHGvm5E7Axtrs6B6-V4nQGCFzcCVJKCM0=wsPtkg@mail.gmail.com' \
--to=alex.kanavin@gmail.com \
--cc=ayaka@soulik.info \
--cc=openembedded-core@lists.openembedded.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.