From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-gnome][PATCH] gvfs-gdu-volume-monitor: Define build dependency on libgnome-keyring
Date: Sun, 20 Apr 2014 13:42:40 +0200 [thread overview]
Message-ID: <20140420114240.GX2486@jama> (raw)
In-Reply-To: <1396031009-15874-1-git-send-email-adam.yh.lee@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
On Fri, Mar 28, 2014 at 11:23:29AM -0700, Adam YH Lee wrote:
> Build fails due to missing libgnome-keyring static library
> (libgnome-keyring.la). libgnome-keyring has to be
> explicitly listed as one of the dependencies.
Merged, thanks!
>
> Signed-off-by: Adam YH Lee <adam.yh.lee@gmail.com>
> ---
> .../gvfs/gvfs-gdu-volume-monitor_1.10.1.bb | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/meta-gnome/recipes-gnome/gvfs/gvfs-gdu-volume-monitor_1.10.1.bb b/meta-gnome/recipes-gnome/gvfs/gvfs-gdu-volume-monitor_1.10.1.bb
> index bd6d9de..cf0ab0c 100644
> --- a/meta-gnome/recipes-gnome/gvfs/gvfs-gdu-volume-monitor_1.10.1.bb
> +++ b/meta-gnome/recipes-gnome/gvfs/gvfs-gdu-volume-monitor_1.10.1.bb
> @@ -2,8 +2,7 @@ require gvfs.inc
>
> BPN = "gvfs"
>
> -DEPENDS = "gvfs gnome-disk-utility"
> -
> +DEPENDS = "gvfs gnome-disk-utility libgnome-keyring"
> PR = "${INC_PR}.0"
>
> # we need gdu files only: reduce files to delete in libexecdir
> --
> 1.7.9.5
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2014-04-20 11:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 18:23 [meta-gnome][PATCH] gvfs-gdu-volume-monitor: Define build dependency on libgnome-keyring Adam YH Lee
2014-04-20 11:42 ` Martin Jansa [this message]
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=20140420114240.GX2486@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@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.