From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] glibmm: new package
Date: Tue, 23 Apr 2013 11:20:39 -0300 [thread overview]
Message-ID: <517698B7.1050405@zacarias.com.ar> (raw)
In-Reply-To: <1366726167-3396-1-git-send-email-nicolas.menegale@openwide.fr>
On 04/23/2013 11:09 AM, nmenegale wrote:
> +++ b/package/glibmm/Config.in
> @@ -0,0 +1,8 @@
> +config BR2_PACKAGE_GLIBMM
> + bool "glibmm"
> + select BR2_PACKAGE_LIBGLIB2
> + select BR2_PACKAGE_LIBSIGC
> + help
> + The GLibmm package is a set of C++ bindings for GLib.
> +
> + http://www.gtkmm.org/
This should depend on BR2_INSTALL_LIBSTDCPP since it requires a
toolchain with C++ support, with a comment otherwise like other packages
do (look at package/protobuf/Config.in for an example).
Same case with libxml++.
> +++ b/package/glibmm/glibmm.mk
> @@ -0,0 +1,13 @@
> +#############################################################
> +#
> +# Glibmm
> +#
> +#############################################################
> +GLIBMM_VERSION = 2.30.1
> +GLIBMM_LICENSE = LGPLv2.1
> +GLIBMM_SOURCE = glibmm-$(GLIBMM_VERSION).tar.bz2
> +GLIBMM_SITE = http://ftp.gnome.org/pub/gnome/sources/glibmm/2.30
> +GLIBMM_INSTALL_STAGING = YES
> +GLIBMM_DEPENDENCIES = libglib2 libsigc host-pkgconf
> +
> +$(eval $(autotools-package))
You define GLIBMM_LICENSE but no GLIBMM_LICENSE_FILES, could you fix
that since glibmm ships them?
libglib2 depends on BR2_USE_WCHAR, you should add that too as a depend
in Config.in
Otherwise it's looking good, thanks.
Regards.
next prev parent reply other threads:[~2013-04-23 14:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 14:09 [Buildroot] [PATCH 1/2] glibmm: new package nmenegale
2013-04-23 14:09 ` [Buildroot] [PATCH 2/2] libxml++: " nmenegale
2013-04-23 14:20 ` Gustavo Zacarias [this message]
2013-04-23 14:31 ` [Buildroot] [PATCH 1/2] glibmm: " Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2013-04-24 8:13 nmenegale
2013-04-24 14:02 ` Thomas Petazzoni
2013-04-24 14:03 ` Thomas Petazzoni
2013-04-24 19:43 ` Peter Korsgaard
2013-04-24 15:11 nmenegale
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=517698B7.1050405@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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