From: Arnout Vandecappelle <arnout@mind.be>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>, buildroot@buildroot.org
Cc: Fabrice Fontaine <fabrice.fontaine@orange.com>,
Samuel Martin <s.martin49@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH 1/2] package/minizip: add minizip-zlib support
Date: Wed, 27 Jul 2022 12:02:32 +0200 [thread overview]
Message-ID: <c1c3040b-d429-dcaf-6e97-5f0c8367b48a@mind.be> (raw)
In-Reply-To: <20220108224337.3702128-1-fontaine.fabrice@gmail.com>
Hi Fabrice,
On 08/01/2022 23:43, Fabrice Fontaine wrote:
> Add a virtual package to allow the user to select the minizip provider:
A virtual package should be used when the alternatives are more or less
drop-in replacements. Here, however, they are absolutely not: they install
completely different header files and libraries. There is no way that something
that expects minizip-ng can build with minizip-zlib or vice versa.
In addition, the two can be installed in parallel.
So there's no reason at all to make it a virtual package.
> - the current minizip (which has been renamed minizip-ng since
> https://github.com/zlib-ng/minizip-ng/commit/db95894646b87f6178ceaa389cbdb5b1ba8cd97a)
It would make more sense to switch the existing minizip package to this new
upstream repository.
We could rename the package to minizip-ng, but we generally avoid that. It's
just annoyance for people who upgrade buildroot (legacy handling helps, but it
is still annoying), and there is no benefit at all other than "consistency".
> - the 'legacy' minizip provided by zlib which is still widely supported
> by various opensource packages such as domoticz
We should just add a package minizip-zlib.
> There is no need to add entries in Config.legacy as the previous options
> are kept and the default provider of minizip is minizip-ng.
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
[snip]
> diff --git a/package/minizip-zlib/minizip-zlib.mk b/package/minizip-zlib/minizip-zlib.mk
> new file mode 100644
> index 0000000000..67d4e31f41
> --- /dev/null
> +++ b/package/minizip-zlib/minizip-zlib.mk
> @@ -0,0 +1,24 @@
> +################################################################################
> +#
> +# minizip-zlib
> +#
> +################################################################################
> +
> +MINIZIP_ZLIB_VERSION = 1.2.11
> +MINIZIP_ZLIB_SOURCE = zlib-$(MINIZIP_ZLIB_VERSION).tar.xz
> +MINIZIP_ZLIB_SITE = http://www.zlib.net
> +MINIZIP_ZLIB_LICENSE = Zlib
> +MINIZIP_ZLIB_LICENSE_FILES = README
> +MINIZIP_ZLIB_INSTALL_STAGING = YES
> +MINIZIP_ZLIB_PROVIDES = minizip
> +MINIZIP_ZLIB_SUBDIR = contrib/minizip
> +MINIZIP_ZLIB_AUTORECONF = YES
Please add a comment why autoreconf is needed.
Regards,
Arnout
> +MINIZIP_ZLIB_DEPENDENCIES = zlib
> +
> +ifeq ($(BR2_PACKAGE_MINIZIP_DEMOS),y)
> +MINIZIP_ZLIB_CONF_OPTS += --enable-demos
> +else
> +MINIZIP_ZLIB_CONF_OPTS += --disable-demos
> +endif
> +
> +$(eval $(autotools-package))
[snip]
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-07-27 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 22:43 [Buildroot] [PATCH 1/2] package/minizip: add minizip-zlib support Fabrice Fontaine
2022-01-08 22:43 ` [Buildroot] [PATCH 2/2] package/domoticz: depends on minizip-zlib Fabrice Fontaine
2022-07-27 10:02 ` Arnout Vandecappelle [this message]
2022-07-27 12:05 ` [Buildroot] [PATCH 1/2] package/minizip: add minizip-zlib support Fabrice Fontaine
2022-07-27 12:49 ` Arnout Vandecappelle
2022-07-27 13:12 ` Fabrice Fontaine
2022-07-27 13:31 ` Arnout Vandecappelle
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=c1c3040b-d429-dcaf-6e97-5f0c8367b48a@mind.be \
--to=arnout@mind.be \
--cc=buildroot@buildroot.org \
--cc=fabrice.fontaine@orange.com \
--cc=fontaine.fabrice@gmail.com \
--cc=s.martin49@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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;
as well as URLs for NNTP newsgroup(s).