Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marton Balint <cus@passwd.hu>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 4/4] Revert "fftools/resources: Add resource manager files with build-time compression"
Date: Sat, 14 Jun 2025 18:11:27 +0200 (CEST)
Message-ID: <5254d4ce-9819-b984-574d-16feac92537c@passwd.hu> (raw)
In-Reply-To: <CABPLASTW32A+ePzTps4rsJ5+zj47W8QGpD7OqLNtuuxSrnO13w@mail.gmail.com>



On Sat, 14 Jun 2025, Kacper Michajlow wrote:

> On Sat, 17 May 2025 at 01:11, Marton Balint <cus@passwd.hu> wrote:
>>
>> This reverts commit 517a8055655798970d94a4c5ea912511362520ea.
>>
>> Building resources directly in the ffmpeg util needs quite a bit of code,
>> increases binary size and makes it harder for the users to change those
>> resources at will.
>>
>> The only user of this, the mermaid and mermaidhtml graph formats were converted
>> in an erlier commit to use file loading from the FFMPEG data dirs similar to
>> ffpreset files. Therefore the infrastucture to build resources directly into
>> ffmpeg CLI tools can be removed now.
>>
>> Signed-off-by: Marton Balint <cus@passwd.hu>
>> ---
>>  configure                    |   5 -
>>  ffbuild/common.mak           |  43 +------
>>  fftools/Makefile             |   5 +-
>>  fftools/resources/.gitignore |   4 -
>>  fftools/resources/Makefile   |  13 --
>>  fftools/resources/resman.c   | 231 -----------------------------------
>>  fftools/resources/resman.h   |  50 --------
>>  7 files changed, 3 insertions(+), 348 deletions(-)
>>  delete mode 100644 fftools/resources/.gitignore
>>  delete mode 100644 fftools/resources/Makefile
>>  delete mode 100644 fftools/resources/resman.c
>>  delete mode 100644 fftools/resources/resman.h
>>

[...]

>
> Hi Marton,
>
> Is this still on track to be merged? Resource embedding is broken on
> some Windows builds and not sure if I should care to debug/fix that or
> this code will be nuked anyway?

Softworkz was strongly against nuking it, so I guess it will stay. I am 
not sure if there are pendig fixes for it.

Regards,
Marton
_______________________________________________
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".

      reply	other threads:[~2025-06-14 16:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-16 23:08 [FFmpeg-devel] [PATCH 1/4] fftools/cmdutils: allow arbitrary length paths for preset files Marton Balint
2025-05-16 23:08 ` [FFmpeg-devel] [PATCH 2/4] fftools/cmdutils: factorize loading a file from the datadir Marton Balint
2025-05-16 23:09 ` [FFmpeg-devel] [PATCH 3/4] fftools/graph/graphprint: load CSS and HTML resources from ffmpeg data directories Marton Balint
2025-05-17  2:21   ` softworkz .
2025-05-17  9:13     ` Marton Balint
2025-05-17 17:22       ` softworkz .
2025-05-17 20:33         ` softworkz .
2025-05-16 23:09 ` [FFmpeg-devel] [PATCH 4/4] Revert "fftools/resources: Add resource manager files with build-time compression" Marton Balint
2025-06-14 14:43   ` Kacper Michajlow
2025-06-14 16:11     ` Marton Balint [this message]

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=5254d4ce-9819-b984-574d-16feac92537c@passwd.hu \
    --to=cus@passwd.hu \
    --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