From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 5/7] liboop: Add recipe
Date: Fri, 9 Dec 2016 22:41:21 +0100 [thread overview]
Message-ID: <20161209214121.GF3327@jama> (raw)
In-Reply-To: <20161206023625.12901-3-raj.khem@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1796 bytes --]
On Mon, Dec 05, 2016 at 06:36:23PM -0800, Khem Raj wrote:
> liboop is needed by ruli
liboop-1.0: liboop rdepends on readline, but it isn't a build dependency, missing readline in DEPENDS or PACKAGECONFIG? [build-deps]
liboop-1.0: liboop rdepends on libpcre, but it isn't a build dependency, missing libpcre in DEPENDS or PACKAGECONFIG? [build-deps]
liboop-1.0: liboop rdepends on glib-2.0, but it isn't a build dependency, missing glib-2.0 in DEPENDS or PACKAGECONFIG? [build-deps]
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> meta-oe/recipes-support/liboop/liboop_1.0.bb | 11 +++++++++++
> 1 file changed, 11 insertions(+)
> create mode 100644 meta-oe/recipes-support/liboop/liboop_1.0.bb
>
> diff --git a/meta-oe/recipes-support/liboop/liboop_1.0.bb b/meta-oe/recipes-support/liboop/liboop_1.0.bb
> new file mode 100644
> index 0000000..1af228e
> --- /dev/null
> +++ b/meta-oe/recipes-support/liboop/liboop_1.0.bb
> @@ -0,0 +1,11 @@
> +DESCRIPTION = "Liboop is a low-level event loop management library for POSIX-based operating systems"
> +HOMEPAGE = "http://liboop.org/"
> +LICENSE = "GPL-2.0"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=8b54f38ccbd44feb80ab90e01af8b700"
> +
> +SRC_URI = "http://ftp.debian.org/debian/pool/main/libo/liboop/liboop_${PV}.orig.tar.gz"
> +
> +SRC_URI[md5sum] = "36cb971047d3af02369446f5e0b315a2"
> +SRC_URI[sha256sum] = "34d83c6e0f09ee15cb2bc3131e219747c3b612bb57cf7d25318ab90da9a2d97c"
> +
> +inherit autotools pkgconfig
> --
> 2.10.2
>
> --
> _______________________________________________
> 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: 201 bytes --]
next prev parent reply other threads:[~2016-12-09 21:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 2:36 [meta-gnome][PATCH 3/7] libwnck3: Add missing dependency on gnome-common-native Khem Raj
2016-12-06 2:36 ` [meta-gnome][PATCH 4/7] ruli: Add new package Khem Raj
2016-12-06 2:36 ` [meta-oe][PATCH 5/7] liboop: Add recipe Khem Raj
2016-12-09 21:41 ` Martin Jansa [this message]
2016-12-06 2:36 ` [meta-gnome][PATCH 6/7] gthumb: Add missing dependency on gnome-common-native Khem Raj
2016-12-06 8:56 ` Andreas Müller
2016-12-07 19:40 ` Khem Raj
2016-12-08 12:48 ` Burton, Ross
2016-12-06 2:36 ` [meta-oe][PATCH 7/7] iozone3: Fix parallel build problem 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=20161209214121.GF3327@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.