From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] python-libconfig: new package
Date: Thu, 06 Mar 2014 18:26:23 +0100 [thread overview]
Message-ID: <5318AFBF.4000006@mind.be> (raw)
In-Reply-To: <E1CF8EFE2042404B87DE2B6D662128020ED591A9@KUUMEX10.barco.com>
On 06/03/14 10:05, Derycke, Johan wrote:
> Hi,
>
>> -----Original Message-----
>> From: Arnout Vandecappelle [mailto:arnout at mind.be]
>> Sent: woensdag 5 maart 2014 18:11
>> To: Derycke, Johan; buildroot at busybox.net
>> Subject: Re: [Buildroot] [PATCH 1/2] python-libconfig: new package
>>
>> 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.
>
> Can I use:
>
> comment "python libconfig needs boost"
> depends on !BR2_PACKAGE_BOOST
> depends on BR2_PACKAGE_PYTHON || BR2_PACKAGE_PYTHON3
>
> to avoid the boost "bloatware" being installed behind the back?
No, that's OK. The bloat is only in the source, not in the libary (I
haven't built it yet but I expect it will be in the order of 100K).
I mainly made the remark to trigger you to consider if it is really
needed. But I think I get it now: boost.Python is an alternative for
something like swig or sip. I first thought it was using some of boost's
standard C++ library alternatives.
Regards,
Arnout
>
>>
>> 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
[snip]
--
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-06 17:26 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
[not found] ` <E1CF8EFE2042404B87DE2B6D662128020ED591A9@KUUMEX10.barco.com>
2014-03-06 17:26 ` Arnout Vandecappelle [this message]
-- 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=5318AFBF.4000006@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