From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] python-libconfig: new package
Date: Wed, 05 Mar 2014 18:10:54 +0100 [thread overview]
Message-ID: <53175A9E.3090001@mind.be> (raw)
In-Reply-To: <E1CF8EFE2042404B87DE2B6D662128020ED58B96@KUUMEX10.barco.com>
On 04/03/14 09:32, Derycke, Johan wrote:
> Python bindings to the C++ library libconfig
> https://github.com/cnangel/python-libconfig
>
> Signed-off-by: Johan Derycke <johan.derycke@barco.com>
> ---
> package/python-libconfig/Config.in | 9 +++++++++
> package/python-libconfig/python-libconfig.mk | 21 +++++++++++++++++++++
> 2 files changed, 30 insertions(+)
> create mode 100644 package/python-libconfig/Config.in
> create mode 100644 package/python-libconfig/python-libconfig.mk
>
> diff --git a/package/python-libconfig/Config.in b/package/python-libconfig/Config.in
> new file mode 100644
> index 0000000..7e4f317
> --- /dev/null
> +++ b/package/python-libconfig/Config.in
> @@ -0,0 +1,9 @@
> +config BR2_PACKAGE_PYTHON_LIBCONFIG
> + bool "python-libconfig"
> + depends on BR2_PACKAGE_PYTHON || BR2_PACKAGE_PYTHON3
> + select BR2_PACKAGE_BOOST_PYTHON
You should also select BR2_PACKAGE_BOOST.
You should also depend on boost's toolchain dependencies:
BR2_INSTALL_LIBSTDCPP, BR2_LARGEFILE, BR2_TOOLCHAIN_HAS_THREADS, and add
the corresponding comment.
It's a crying shame that the python wrapper for something trivial like
libconfig requires bloatware like boost :-) but that can't be helped of
course.
> + select BR2_PACKAGE_LIBCONFIG
> + help
> + Python bindings to the C++ library libconfig
Perhaps add a bit of the help text of libconfig.
Regards,
Arnout
> +
> + https://github.com/cnangel/python-libconfig
> diff --git a/package/python-libconfig/python-libconfig.mk b/package/python-libconfig/python-libconfig.mk
> new file mode 100644
> index 0000000..8d597ef
> --- /dev/null
> +++ b/package/python-libconfig/python-libconfig.mk
> @@ -0,0 +1,21 @@
> +################################################################################
> +#
> +# python-libconfig
> +#
> +################################################################################
> +
> +PYTHON_LIBCONFIG_VERSION = b271c3d9dac938ad5cd29b67bd08cc5536a5a391
> +PYTHON_LIBCONFIG_SITE = https://github.com/cnangel/python-libconfig/
> +PYTHON_LIBCONFIG_SITE_METHOD = git
> +
> +PYTHON_LIBCONFIG_LICENSE = BSD
> +PYTHON_LIBCONFIG_LICENSE_FILES = README
> +
> +PYTHON_LIBCONFIG_SETUP_TYPE = setuptools
> +
> +PYTHON_LIBCONFIG_DEPENDENCIES = libconfig boost
> +
> +$(eval $(python-package))
> +
> +
> +
> --
> 1.7.10.4
>
> Best regards,
> Johan Derycke
>
>
>
>
>
> This message is subject to the following terms and conditions: MAIL DISCLAIMER<http://www.barco.com/en/maildisclaimer>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2014-03-05 17:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 8:32 [Buildroot] [PATCH 1/2] python-libconfig: new package Derycke, Johan
2014-03-04 8:47 ` Baruch Siach
2014-03-05 17:10 ` Arnout Vandecappelle [this message]
[not found] ` <E1CF8EFE2042404B87DE2B6D662128020ED591A9@KUUMEX10.barco.com>
2014-03-06 17:26 ` Arnout Vandecappelle
-- strict thread matches above, loose matches on Subject: below --
2014-03-06 9:26 Johan Derycke
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=53175A9E.3090001@mind.be \
--to=arnout@mind.be \
--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