Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] gupnp: new package
Date: Mon, 14 Sep 2015 11:46:58 +0100	[thread overview]
Message-ID: <55F6A5A2.7020901@imgtec.com> (raw)
In-Reply-To: <1442226095-4316-3-git-send-email-rahul.bedarkar@imgtec.com>

Dear Rahul Bedarkar,

On 09/14/2015 11:21 AM, Rahul Bedarkar wrote:
[snip]
> diff --git a/package/gupnp/Config.in b/package/gupnp/Config.in
> new file mode 100644
> index 0000000..89c14fc
> --- /dev/null
> +++ b/package/gupnp/Config.in
> @@ -0,0 +1,20 @@
> +config BR2_PACKAGE_GUPNP
> +	bool "gupnp"
> +	depends on BR2_USE_WCHAR # glib2

util-linux also needs wchar so add it to the list: # glib2, util-linux

> +	depends on BR2_TOOLCHAIN_HAS_THREADS # glib2
> +	depends on BR2_USE_MMU # glib2
> +	select BR2_PACKAGE_LIBGLIB2
> +	select BR2_PACKAGE_GSSDP
> +	select BR2_PACKAGE_LIBXML2
> +	select BR2_PACKAGE_UTIL_LINUX
> +	select BR2_PACKAGE_UTIL_LINUX_LIBUUID
> +	help
> +	  GUPnP implements the UPnP specification: resource announcement
> +	  and discovery, description, control, event notification, and
> +	  presentation.
> +
> +	  http://www.gupnp.org/
> +
> +comment "gupnp needs a toolchain w/ wchar, threads"
> +	depends on BR2_USE_MMU
> +	depends on !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_THREADS
> diff --git a/package/gupnp/gupnp.hash b/package/gupnp/gupnp.hash
> new file mode 100644
> index 0000000..597cb42
> --- /dev/null
> +++ b/package/gupnp/gupnp.hash
> @@ -0,0 +1,2 @@
> +# Hash from: http://ftp.gnome.org/pub/gnome/sources/gupnp/0.19/gupnp-0.19.4.sha256sum:
> +sha256 3c1fb2873cb2f8f152b9d49598d55b15b8f3c1096a03ade46ce69694798fb243  gupnp-0.19.4.tar.xz
> diff --git a/package/gupnp/gupnp.mk b/package/gupnp/gupnp.mk
> new file mode 100644
> index 0000000..07fd851
> --- /dev/null
> +++ b/package/gupnp/gupnp.mk
> @@ -0,0 +1,15 @@
> +################################################################################
> +#
> +# gupnp
> +#
> +################################################################################
> +
> +GUPNP_VERSION = 0.19.4
> +GUPNP_SOURCE = gupnp-$(GUPNP_VERSION).tar.xz
> +GUPNP_SITE = http://ftp.gnome.org/pub/gnome/sources/gupnp/0.19

I think this would be better:

GUPNP_VERSION_MAJOR = 0.19
GUPNP_VERSION = $(GUPNP_VERSION_MAJOR).4
GUPNP_SOURCE = gupnp-$(GUPNP_VERSION).tar.xz
GUPNP_SITE =
http://ftp.gnome.org/pub/gnome/sources/gupnp/$(GUPNP_VERSION_MAJOR)

Regards,

Vincent.

> +GUPNP_LICENSE = LGPLv2+
> +GUPNP_LICENSE_FILES = COPYING
> +GUPNP_INSTALL_STAGING = YES
> +GUPNP_DEPENDENCIES = host-pkgconf libglib2 libxml2 gssdp util-linux
> +
> +$(eval $(autotools-package))
> 

  reply	other threads:[~2015-09-14 10:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14 10:21 [Buildroot] [PATCH 0/3] new packages gssdp, gupnp and gupnp-av Rahul Bedarkar
2015-09-14 10:21 ` [Buildroot] [PATCH 1/3] gssdp: new package Rahul Bedarkar
2015-09-14 10:43   ` Vicente Olivert Riera
2015-09-14 10:21 ` [Buildroot] [PATCH 2/3] gupnp: " Rahul Bedarkar
2015-09-14 10:46   ` Vicente Olivert Riera [this message]
2015-09-14 10:21 ` [Buildroot] [PATCH 3/3] gupnp-av: " Rahul Bedarkar
2015-09-14 10:50   ` Vicente Olivert Riera

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=55F6A5A2.7020901@imgtec.com \
    --to=vincent.riera@imgtec.com \
    --cc=buildroot@busybox.net \
    /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