From: "Jörg Krause" <jkrause@posteo.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] libupnpp: new package
Date: Mon, 20 Oct 2014 23:24:32 +0200 [thread overview]
Message-ID: <54457D90.6060302@posteo.de> (raw)
In-Reply-To: <20141020175011.GI3742@free.fr>
Yann, All,
On 10/20/2014 07:50 PM, Yann E. MORIN wrote:
> J?rg, All,
>
> On 2014-10-20 19:43 +0200, Yann E. MORIN spake thusly:
>> On 2014-10-20 15:50 +0200, J?rg Krause spake thusly:
>>> Signed-off-by: J?rg Krause <jkrause@posteo.de>
>> [--SNIP--]
>>> diff --git a/package/libupnpp/Config.in b/package/libupnpp/Config.in
>>> new file mode 100644
>>> index 0000000..5a79452
>>> --- /dev/null
>>> +++ b/package/libupnpp/Config.in
>>> @@ -0,0 +1,20 @@
>>> +config BR2_PACKAGE_LIBUPNPP
>>> + bool "libupnpp"
>>> + select BR2_PACKAGE_EXPAT
>>> + select BR2_PACKAGE_LIBCURL
>>> + select BR2_PACKAGE_LIBUPNP
>>> + depends on BR2_INSTALL_LIBSTDCPP
>>> + depends on BR2_LARGEFILE # libupnp
>>> + depends on BR2_TOOLCHAIN_HAS_THREADS # libupnp
>>> + depends on !BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2014R1 # Too old gcc
>>> + depends on !BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2013R1 # Ditto
>>> + depends on !BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R2 # Ditto
>> Nice! It proves you did quite some testing! :-)
> I withdraw that comment: the dependencies were copied as-is from
> upmpdcli. Are they still required for libupnpp?
I've checked this. They are still required. gcc 4.3.5 does not support
C++11 keyword `auto`.
>
>>> + help
>>> + The libupnpp C++ library wraps libupnp for easier use by upmpdcli and
>>> + upplay.
>>> +
>>> + http://www.lesbonscomptes.com/upmpdcli/
>>> +
>>> +comment "upmpdcli needs a toolchain w/ C++, largefile, threads"
>> 'upmpdcli', really?
Copy & paste error. Fixed!
>>
>> Otherwise, looks good. With the above mishap fixed, you can add my:
>>
>> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Sorry, I withdraw my rev tag, because of the above. That's what you get
> by not reviewing the whole series before replying to a patch...
> Sorry... :-(
>
> J"org, that does not mean this is faulty, I just wnat to have an answer
> to the above before I can give my rev tag.
>
I will submit a fixed patch.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20141020/dfec6f2b/attachment.html>
prev parent reply other threads:[~2014-10-20 21:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 13:50 [Buildroot] [PATCH 1/2] libupnpp: new package Jörg Krause
2014-10-20 13:50 ` [Buildroot] [PATCH 2/2] package/upmpdcli: bump to version 0.8.5 Jörg Krause
2014-10-20 17:46 ` Yann E. MORIN
2014-10-20 17:43 ` [Buildroot] [PATCH 1/2] libupnpp: new package Yann E. MORIN
2014-10-20 17:50 ` Yann E. MORIN
2014-10-20 21:24 ` Jörg Krause [this message]
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=54457D90.6060302@posteo.de \
--to=jkrause@posteo.de \
--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