From: akuster808 <akuster808@gmail.com>
To: "Hongzhi.Song" <hongzhi.song@windriver.com>,
openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] snappy: add a new recipe
Date: Wed, 25 Jul 2018 08:35:56 -0700 [thread overview]
Message-ID: <3ebaef51-c4d7-e384-ac17-158e732263d3@gmail.com> (raw)
In-Reply-To: <20180725103604.10463-1-hongzhi.song@windriver.com>
On 07/25/2018 03:36 AM, Hongzhi.Song wrote:
> Snappy is a compression/decompression library. It does not aim for
> maximum compression, or compatibility with any other compression
> library; instead, it aims for very high speeds and reasonable compression.
>
> Signed-off-by: Hongzhi.Song <hongzhi.song@windriver.com>
> ---
> meta-oe/recipes-extended/snappy/snappy_1.1.7.bb | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
> create mode 100644 meta-oe/recipes-extended/snappy/snappy_1.1.7.bb
>
> diff --git a/meta-oe/recipes-extended/snappy/snappy_1.1.7.bb b/meta-oe/recipes-extended/snappy/snappy_1.1.7.bb
> new file mode 100644
> index 000000000..0fca4ccaf
> --- /dev/null
> +++ b/meta-oe/recipes-extended/snappy/snappy_1.1.7.bb
> @@ -0,0 +1,20 @@
> +#
> +# Copyright (C) 2014 Wind River Systems, Inc.
> +#
> +SUMMARY = "A compression/decompression library"
> +DESCRIPTION = "Snappy is a fast data compression and decompression library \
> +It was designed to be very fast and stable, but not to achieve a high \
> +compression ratio."
> +
> +LICENSE = "NewBSD"
Is this LICENSE somewhere ?
- armin
> +LIC_FILES_CHKSUM = "file://COPYING;md5=f62f3080324a97b3159a7a7e61812d0c"
> +
> +SRC_URI = "https://src.fedoraproject.org/repo/pkgs/snappy/snappy-1.1.7.tar.gz/sha512/32046f532606ba545a4e4825c0c66a19be449f2ca2ff760a6fa170a3603731479a7deadb683546e5f8b5033414c50f4a9a29f6d23b7a41f047e566e69eca7caf/snappy-1.1.7.tar.gz"
> +
> +SRC_URI[md5sum] = "ee9086291c9ae8deb4dac5e0b85bf54a"
> +SRC_URI[sha256sum] = "3dfa02e873ff51a11ee02b9ca391807f0c8ea0529a4924afa645fbf97163f9d4"
> +
> +inherit cmake pkgconfig
> +
> +PACKAGECONFIG ??= ""
> +PACKAGECONFIG[lzo] = "-DHAVE_LIBLZO2=1,-DHAVE_LIBLZO2=0,lzo,"
next prev parent reply other threads:[~2018-07-25 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 10:36 [meta-oe][PATCH] snappy: add a new recipe Hongzhi.Song
2018-07-25 15:35 ` akuster808 [this message]
2018-07-25 20:30 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2018-07-26 5:57 Hongzhi.Song
2018-07-26 6:02 ` Hongzhi, Song
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=3ebaef51-c4d7-e384-ac17-158e732263d3@gmail.com \
--to=akuster808@gmail.com \
--cc=hongzhi.song@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
/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