Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH v3 08/11] libinih: add git recipe
Date: Sun, 08 May 2011 20:36:18 +0200	[thread overview]
Message-ID: <iq6nr2$ppo$1@dough.gmane.org> (raw)
In-Reply-To: <1304872895-21596-8-git-send-email-otavio@ossystems.com.br>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08-05-11 18:41, Otavio Salvador wrote:
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
>  meta-oe/recipes-support/inih/libinih_git.bb |   20 ++++++++++++++++++++
>  1 files changed, 20 insertions(+), 0 deletions(-)
>  create mode 100644 meta-oe/recipes-support/inih/libinih_git.bb
> 
> diff --git a/meta-oe/recipes-support/inih/libinih_git.bb b/meta-oe/recipes-support/inih/libinih_git.bb
> new file mode 100644
> index 0000000..1dc2059
> --- /dev/null
> +++ b/meta-oe/recipes-support/inih/libinih_git.bb
> @@ -0,0 +1,20 @@
> +DESCRIPTION = "C and C++ INI Library"
> +HOMEPAGE = "http://code.google.com/p/inih/"
> +PRIORITY = "optional"
> +PV = "0.0+gitr${SRCPV}"
> +PKGV = "${GITPKGVTAG}"
> +LICENSE = "BSD"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=dae28cbf28207425e0d0b3eb835f4bde"
> +
> +PR = "r0"
> +
> +# The github repository provides a cmake and pkg-config integration
> +SRCREV = "715cb4dc3d56714d7d53dcd94ae4b41c950119a7"
> +SRC_URI = "git://github.com/OSSystems/inih.git;protocol=git"
> +
> +S = "${WORKDIR}/git"
> +
> +inherit gitpkgv cmake
> +
> +# We don't have libinih since we only have static libraries
> +RDEPENDS_${PN}-dev = ""

ALLOW_EMPTY_${PN} = "1" would be better, since that doesn't break the
automatic depchain code
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFNxuKiMkyGM64RGpERAgjbAKCJHErAGUNq7yOnjj5u/Qp6YfpKIgCdFu6B
qnXoflMuORS6H6e3K+R1sMw=
=KvqY
-----END PGP SIGNATURE-----




  reply	other threads:[~2011-05-08 18:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-08 16:41 [meta-oe][PATCH v3 01/11] fuse: add version 2.8.5 Otavio Salvador
2011-05-08 16:41 ` [meta-oe][PATCH v3 02/11] ntfs-3g-ntfsprogs: add version 2011.4.12 Otavio Salvador
2011-05-08 16:41 ` [meta-oe][PATCH v3 03/11] setxkbmap: add version 1.2.0 Otavio Salvador
2011-05-08 16:41 ` [meta-oe][PATCH v3 04/11] freerdp: add recipe based on GIT from 2009-03-29 Otavio Salvador
2011-05-08 16:41 ` [meta-oe][PATCH v3 05/11] pixman.inc: use Xorg mirror Otavio Salvador
2011-05-08 16:41 ` [meta-oe][PATCH v3 06/11] p910nd: add version 0.95 Otavio Salvador
2011-05-09 13:58   ` Phil Blundell
2011-05-09 14:06     ` Otavio Salvador
2011-05-09 14:11       ` Phil Blundell
2011-05-08 16:41 ` [meta-oe][PATCH v3 07/11] libiconv: drop hack since gettext was being inherited Otavio Salvador
2011-05-08 16:41 ` [meta-oe][PATCH v3 08/11] libinih: add git recipe Otavio Salvador
2011-05-08 18:36   ` Koen Kooi [this message]
2011-05-08 16:41 ` [meta-oe][PATCH v3 09/11] qt4: drop 4.6 versions Otavio Salvador
2011-05-08 16:41 ` [meta-oe][PATCH v3 10/11] postgresql: update to 8.4.7 since 8.4.4 was unfetchable Otavio Salvador
2011-05-08 16:41 ` [meta-oe][PATCH v3 11/11] qt4: fix 4.7.2 checksum Otavio Salvador
2011-05-08 18:34 ` [meta-oe][PATCH v3 01/11] fuse: add version 2.8.5 Koen Kooi

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='iq6nr2$ppo$1@dough.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox