Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v3] ffbuild: read library linker objects from a file
Date: Mon, 17 Mar 2025 15:21:01 +0200 (EET)
Message-ID: <218819b-f6ea-93cf-151-5bd76c143a64@martin.st> (raw)
In-Reply-To: <a34c8235-01f1-4ad2-b12e-423a9ed94079@gyani.pro>

On Mon, 17 Mar 2025, Gyan Doshi wrote:

> On 2025-03-17 05:29 pm, Zhao Zhili wrote:
>>
>>>> @file doesn’t supported by ar on macOS or BSD.
>>> Do we have any FATE clients on these platforms?
>> I remember there were apple machines, but they are not there now.
>>
>> https://fate.ffmpeg.org/
>
> Can we get a definite list of archiver/linkers which we support that 
> don't support response files?

Wouldn't it be easier to just test within configure whether $AR supports 
response files like this? And then emit a flag to config.mak which allows 
picking which codepath to take here.

Alternatively we could look for specifically targeting the fix to Windows 
- however, it's not enough to look for the target OS - it needs to look at 
the host OS. Crosscompiling for Windows on unix won't need it, and the 
converse, crosscompiling on Windows targeting Linux would also need the 
same fix.

So just checking whether the feature is supported by $AR might be the 
simplest.

// Martin
_______________________________________________
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-03-17 13:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13 13:02 Gyan Doshi
2025-03-15  7:56 ` Gyan Doshi
2025-03-17 10:17   ` Gyan Doshi
2025-03-17 11:32 ` Zhao Zhili
2025-03-17 11:45   ` Gyan Doshi
2025-03-17 11:59     ` Zhao Zhili
2025-03-17 13:11       ` Gyan Doshi
2025-03-17 13:21         ` Martin Storsjö [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=218819b-f6ea-93cf-151-5bd76c143a64@martin.st \
    --to=martin@martin.st \
    --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