From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: kai <kai.kang@windriver.com>, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] gcr: depends on gnupg-native
Date: Thu, 14 May 2020 14:26:50 +0100 [thread overview]
Message-ID: <9c5dcfc03d2670a447cc08565cb74e407211906a.camel@linuxfoundation.org> (raw)
In-Reply-To: <f00e9d2b-8ada-a259-337d-9c1fa37862ab@windriver.com>
On Thu, 2020-05-14 at 09:59 +0800, kai wrote:
> On 2020/5/11 下午5:23, kai.kang@windriver.com wrote:
> > From: Kai Kang <kai.kang@windriver.com>
> >
> > It fails to build gcr if no commmand gpg on build host:
> >
> > > meson.build:44:0: ERROR: Program(s) ['gpg2', 'gpg'] not found or
> > > not executable
> >
> > Add dependency gnupg-native to fix the error.
> >
> > Signed-off-by: Kai Kang <kai.kang@windriver.com>
> > ---
> > meta/recipes-gnome/gcr/gcr_3.36.0.bb | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-gnome/gcr/gcr_3.36.0.bb b/meta/recipes-
> > gnome/gcr/gcr_3.36.0.bb
> > index 4fe3b2fff3..458dc8e6c4 100644
> > --- a/meta/recipes-gnome/gcr/gcr_3.36.0.bb
> > +++ b/meta/recipes-gnome/gcr/gcr_3.36.0.bb
> > @@ -8,7 +8,7 @@ BUGTRACKER = "
> > https://gitlab.gnome.org/GNOME/gcr/issues"
> > LICENSE = "GPLv2"
> > LIC_FILES_CHKSUM =
> > "file://COPYING;md5=55ca817ccb7d5b5b66355690e9abc605"
> >
> > -DEPENDS = "gtk+3 p11-kit glib-2.0 libgcrypt \
> > +DEPENDS = "gtk+3 p11-kit glib-2.0 libgcrypt gnupg-native \
> > ${@bb.utils.contains('GI_DATA_ENABLED', 'True',
> > 'libxslt-native', '', d)}"
> >
> > GNOMEBASEBUILDCLASS = "meson"
>
> Any comment, please?
Why did this happen? Was this as a result of the move to meson? Is it
really needed and can we avoid it? native dependencies like this are a
pain from a build performance perspective...
Cheers,
Richard
next prev parent reply other threads:[~2020-05-14 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 9:23 [PATCH] gcr: depends on gnupg-native kai
2020-05-14 1:59 ` kai
2020-05-14 13:26 ` Richard Purdie [this message]
2020-05-14 17:29 ` [OE-core] " Alexander Kanavin
2020-05-15 1:51 ` kai
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=9c5dcfc03d2670a447cc08565cb74e407211906a.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=kai.kang@windriver.com \
--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.