From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH WIP 01/10] ffbuild/bin2c: Use zlib directly instead of gzip
Date: Wed, 11 Jun 2025 03:05:14 +0000
Message-ID: <DM8P223MB0365913751D9E596378A399FBA75A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <GV1P250MB073793B6D428D364887AC5DD8F6DA@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Andreas Rheinhardt
> Sent: Dienstag, 3. Juni 2025 16:34
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH WIP 01/10] ffbuild/bin2c: Use zlib
> directly instead of gzip
>
Hi Andreas,
thinking about the direction of this patchset, I came to this idea:
How about ditching zlib altogether for this and replace it with some
compact compression code right away?
Something like these might be suitable:
https://github.com/ariya/FastLZ/blob/master/fastlz.c
https://github.com/richgel999/miniz/blob/master/miniz.c
(licenses should be compatible for including the code)
This would solve both problems:
- zlib detection during build
- zlib being unavailable at runtime when linked dynamically
How do you think about this?
I think it wouldn't matter when the compression is slightly less effective..
Best regards
sw
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-06-11 3:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 2:38 Andreas Rheinhardt
2025-06-02 3:22 ` softworkz .
2025-06-02 22:33 ` softworkz .
2025-06-03 14:33 ` Andreas Rheinhardt
2025-06-03 14:47 ` softworkz .
2025-06-11 3:05 ` softworkz . [this message]
2025-06-16 18:51 ` Andreas Rheinhardt
2025-06-16 19:15 ` softworkz .
2025-06-16 19:24 ` Andreas Rheinhardt
2025-06-16 20:18 ` softworkz .
2025-06-16 22:15 ` Andreas Rheinhardt
2025-06-17 9:29 ` Nicolas George
2025-06-17 13:23 ` softworkz .
2025-06-17 14:09 ` Nicolas George
2025-06-17 14:35 ` softworkz .
2025-06-17 14:40 ` Nicolas George
2025-06-17 14:41 ` James Almer
2025-06-17 14:51 ` softworkz .
2025-06-18 7:09 ` Nicolas George
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=DM8P223MB0365913751D9E596378A399FBA75A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
--to=softworkz-at-hotmail.com@ffmpeg.org \
--cc=ffmpeg-devel@ffmpeg.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git