From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mplayer: needs zlib
Date: Wed, 14 Oct 2015 10:56:20 -0300 [thread overview]
Message-ID: <561E5F04.9020607@zacarias.com.ar> (raw)
In-Reply-To: <20151013225708.3aa5e0aa@free-electrons.com>
On 13/10/15 17:57, Thomas Petazzoni wrote:
> While this solution is simple, I am not sure if this is the right one.
> It is in fact perfectly possible to build mplayer without zlib, by
> doing:
>
> +MPLAYER_CONF_OPTS += --disable-decoder=apng --disable-encoder=apng --disable-decoder=tdsc
>
> So in fact, zlib is only needed for two decoders/encoders in the ffmpeg
> code. However, it is not really clear to me how to handle this
> properly: there is one configure script at the top-level directory, and
> then another one in the ffmpeg/ directory. And it is really the ffmpeg
> encoders/decoders that have this zlib requirement (and probably
> others?).
>
> So, simple solution is to make zlib mandatory (which is reasonable:
> zlib is small, and probably already part of most systems). However, I
> wonder if there are not some other dependencies for certain
> encoders/decoders.
>
> Bernd, Gustavo, do you have some suggestions ?
Hi Bernd, Thomas, Vicente.
Both apng and tdsc are on the same family of codecs, they're basically
animated-image formats, apng being animated png, and tdsc being a form
of animated jpeg.
Since in general we don't require any special deps for mplayer (and it
doesn't require them most of the time) i'd say being able to build
without zlib would be desirable, specially since these formats are
unlikely to normally be used via mplayer (they probably weren't an
available feature with 1.1.x)
So using an autodep on zlib seems better IMO.
Regards.
next prev parent reply other threads:[~2015-10-14 13:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 9:58 [Buildroot] [PATCH] mplayer: needs zlib Vicente Olivert Riera
2015-10-13 20:57 ` Thomas Petazzoni
2015-10-14 13:56 ` Gustavo Zacarias [this message]
2015-10-14 14:07 ` Vicente Olivert Riera
2015-10-14 14:09 ` Gustavo Zacarias
2015-10-14 14:16 ` Vicente Olivert Riera
2015-10-13 20:59 ` Yann E. MORIN
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=561E5F04.9020607@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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