From: Sebastien Bourdelin <sebastien.bourdelin@savoirfairelinux.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] yaml-cpp: new package
Date: Mon, 20 Oct 2014 10:57:25 -0400 [thread overview]
Message-ID: <544522D5.3080509@savoirfairelinux.com> (raw)
In-Reply-To: <20141019151116.GV4072@free.fr>
Hi Yann,
Thanks for your review.
On 10/19/2014 11:11 AM, Yann E. MORIN wrote:
> Sebastien, All,
>
> On 2014-10-16 10:48 -0400, Sebastien Bourdelin spake thusly:
>> yaml-cpp is a YAML parser and emitter in C++ matching
>> the YAML 1.2 spec.
>>
>> https://code.google.com/p/yaml-cpp/
>>
>> Signed-off-by: Sebastien Bourdelin <sebastien.bourdelin@savoirfairelinux.com>
> [--SNIP--]
>> diff --git a/package/yaml-cpp/Config.in b/package/yaml-cpp/Config.in
>> new file mode 100644
>> index 0000000..fcfd60f
>> --- /dev/null
>> +++ b/package/yaml-cpp/Config.in
>> @@ -0,0 +1,14 @@
>> +config BR2_PACKAGE_YAML_CPP
>> + bool "yaml-cpp"
>> + depends on BR2_INSTALL_LIBSTDCPP
>> + depends on BR2_LARGEFILE
>> + depends on BR2_TOOLCHAIN_HAS_THREADS
>> + select BR2_PACKAGE_BOOST
> Are BR2_LARGEFILE and BR2_TOOLCHAIN_HAS_THREADS hard dependencies of
> yaml-cpp, or are they inherited from boost?
Yes dependencies are inherited from boost.
I will send an other patch.
> In the latter case, it should be documented, like so:
>
> depends on BR2_LARGEFILE # boost
> depends on BR2_TOOLCHAIN_HAS_THREADS # boost
>
>> + help
>> + yaml-cpp is a YAML parser and emitter in C++ matching
>> + the YAML 1.2 spec.
>> +
>> + https://code.google.com/p/yaml-cpp/
>> +
>> +comment "yaml-cpp needs a toolchain w/ C++, largefile, threads"
>> + depends on !BR2_INSTALL_LIBSTDCPP || !BR2_LARGEFILE || !BR2_TOOLCHAIN_HAS_THREADS
>> diff --git a/package/yaml-cpp/yaml-cpp.hash b/package/yaml-cpp/yaml-cpp.hash
>> new file mode 100644
>> index 0000000..391e317
>> --- /dev/null
>> +++ b/package/yaml-cpp/yaml-cpp.hash
>> @@ -0,0 +1,5 @@
>> +# hash from: https://yaml-cpp.googlecode.com/files/yaml-cpp-0.5.1.tar.gz:
>> +sha1 9c5414b4090491e96d1b808fe8628b31e625fdaa yaml-cpp-0.5.1.tar.gz
>> +
>> +# Locally calculated:
>> +sha256 3e7c9052b43d987d41819a203d97fc45de4eed3ec67e0fdb14265c3d11046f06 yaml-cpp-0.5.1.tar.gz
>> diff --git a/package/yaml-cpp/yaml-cpp.mk b/package/yaml-cpp/yaml-cpp.mk
> Both hash locally and manually verified.
>
> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
>
> Regards,
> Yann E. MORIN.
>
>> new file mode 100644
>> index 0000000..5ebdb23
>> --- /dev/null
>> +++ b/package/yaml-cpp/yaml-cpp.mk
>> @@ -0,0 +1,13 @@
>> +################################################################################
>> +#
>> +# yaml-cpp
>> +#
>> +################################################################################
>> +
>> +YAML_CPP_VERSION = 0.5.1
>> +YAML_CPP_SITE = https://yaml-cpp.googlecode.com/files
>> +YAML_CPP_INSTALL_STAGING = YES
>> +YAML_CPP_LICENSE = MIT
>> +YAML_CPP_LICENSE_FILES = license.txt
>> +
>> +$(eval $(cmake-package))
>> --
>> 1.8.3.4
>>
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
Regards,
Sebastien Bourdelin.
prev parent reply other threads:[~2014-10-20 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 14:48 [Buildroot] [PATCH v2] yaml-cpp: new package Sebastien Bourdelin
2014-10-19 15:11 ` Yann E. MORIN
2014-10-20 14:57 ` Sebastien Bourdelin [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=544522D5.3080509@savoirfairelinux.com \
--to=sebastien.bourdelin@savoirfairelinux.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