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: Tue, 3 Jun 2025 14:47:30 +0000 Message-ID: <DM8P223MB0365B3773E94805B95E2B6EEBA6DA@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 > > softworkz .: > > > > > >> -----Original Message----- > >> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Andreas > >> Rheinhardt > >> Sent: Montag, 2. Juni 2025 04:39 > >> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> > >> Subject: [FFmpeg-devel] [PATCH WIP 01/10] ffbuild/bin2c: Use zlib directly > >> instead of gzip > >> > >> This is a WIP patchset to further improve the resource manager. The > >> configure bits are the one that need more work: How do we detect zlib > >> (and the required library to link to) on the host system? > >> > > > > Hi, > > > > I ran CI builds for the whole Patchset > > https://github.com/ffstaging/FFmpeg/pull/91 > > > > > > Mac build fails (all others are fine) > > > https://dev.azure.com/githubsync/ffmpeg/_build/results?buildId=91751&view=logs > > > > > > > > Undefined symbols for architecture x86_64: > > Undefined symbols for architecture x86_64: > > "_ff_vf_yadif_videotoolbox_metallib_len", referenced from: > > _do_init in libavfilter.a[397](vf_yadif_videotoolbox.o) > > ld: symbol(s) not found for architecture x86_64 > > clang: error: linker command failed with exit code 1 (use -v to see > invocation) > > make: *** [ffprobe_g] Error 1 > > "_ff_vf_yadif_videotoolbox_metallib_len", referenced from: > > _do_init in libavfilter.a[397](vf_yadif_videotoolbox.o) > > ld: symbol(s) not found for architecture x86_64 > > clang: error: linker command failed with exit code 1 (use -v to see > invocation) > > make: *** [ffplay_g] Error 1 > > > > Thanks for the test. I overlooked that this was also used by metal. > Updated version attached and also available at > https://github.com/mkver/FFmpeg/tree/bin2c. Thanks, I re-pushed and PRed it here: https://github.com/ffstaging/FFmpeg/pull/92 (will take up to 1h until all builds are through) > Btw: The non-bin2c patches > are actually logically independent from the bin2c patches and don't need > to wait for them (there will be rebase conflicts when changing the > order, but fixing them would be on me). From my side, there's no urgency in this, it can wait until you got it all together. > The metal bits are untested, but should work. I don't have a mac, so I can't test locally. Not sure whether FATE is including some metal tests? Then I could try enabling HW tests on the builder.. > I have not worked on the configure bits. I'm totally clueless in that area, unfortunately 😊 Best 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-03 14:47 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 . [this message] 2025-06-11 3:05 ` softworkz . 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=DM8P223MB0365B3773E94805B95E2B6EEBA6DA@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