From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] ffbuild: compose linker response files in a loop
Date: Fri, 21 Mar 2025 23:59:13 +0200 (EET)
Message-ID: <b8df6d89-2f93-5031-1b1c-1e1f2a141841@martin.st> (raw)
In-Reply-To: <20250321104136.54347-1-ffmpeg@gyani.pro>
On Fri, 21 Mar 2025, Gyan Doshi wrote:
> Avoids echo failing due to the same ARG_MAX limit that prompted
> response files to be used with the linker.
I presume this is only a fix for a hypothetical issue, _if_ echo would be
a native windows executable and not the msys2/cygwin one which bypasses
the limit?
> ---
> ffbuild/library.mak | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/ffbuild/library.mak b/ffbuild/library.mak
> index 7e1871b74c..15302852ec 100644
> --- a/ffbuild/library.mak
> +++ b/ffbuild/library.mak
> @@ -36,7 +36,8 @@ endif
> $(SUBDIR)$(LIBNAME): $(OBJS) $(STLIBOBJS)
> $(RM) $@
> ifeq ($(AR_OBJS),true)
> - $(Q)echo $^ > $@.objs
> + -$(RM) $@.objs
> + $(Q)$(foreach ARG,$^,echo -n "$(ARG) " >> $@.objs;)
Does this instance even work, it looks broken, like it is missing
something?
> $(AR) $(ARFLAGS) $(AR_O) @$@.objs
> else
> $(AR) $(ARFLAGS) $(AR_O) $^
> @@ -73,7 +74,9 @@ $(SUBDIR)$(SLIBNAME): $(SUBDIR)$(SLIBNAME_WITH_MAJOR)
> $(SUBDIR)$(SLIBNAME_WITH_MAJOR): $(OBJS) $(SHLIBOBJS) $(SLIBOBJS) $(SUBDIR)lib$(NAME).ver
> $(SLIB_CREATE_DEF_CMD)
> ifeq ($(AR_OBJS),true)
> - $(Q)echo $$(filter %.o,$$^) > $$@.objs
> + -$(RM) $$@.objs
> + $(Q)$(eval LDARGS=$$(filter %.o,$$^))
> + $(Q)$(foreach ARG,$$(LDARGS),echo -n "$(ARG) " >> $$@.objs;)
Wouldn't this be quite significantly slow on msys2, where process creation
is much slower than on unix? I think it's not worth to make things that
much slower (which I only guess here) to fix a hypothetical issue.
// 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".
next prev parent reply other threads:[~2025-03-21 21:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-21 10:40 Gyan Doshi
2025-03-21 10:40 ` [FFmpeg-devel] [PATCH 2/2] configure: add option to select use of response files Gyan Doshi
2025-03-25 11:51 ` Ramiro Polla
2025-03-26 14:08 ` [FFmpeg-devel] [PATCH v2] " Gyan Doshi
2025-03-29 5:12 ` Gyan Doshi
2025-03-30 14:10 ` Gyan Doshi
2025-03-21 21:59 ` Martin Storsjö [this message]
2025-03-22 4:33 ` [FFmpeg-devel] [PATCH 1/2] ffbuild: compose linker response files in a loop Gyan Doshi
2025-03-25 11:41 ` Ramiro Polla
2025-03-26 14:12 ` Gyan Doshi
2025-03-26 18:07 ` Andreas Rheinhardt
2025-03-27 4:33 ` Gyan Doshi
2025-03-29 5:11 ` Gyan Doshi
2025-03-29 12:21 ` Ramiro Polla
2025-03-29 14:25 ` Gyan Doshi
2025-03-29 18:22 ` Martin Storsjö
2025-03-30 5:02 ` Gyan Doshi
2025-03-30 5:09 ` Christopher Snowhill
2025-03-30 6:27 ` Andreas Rheinhardt
2025-03-30 6:53 ` Gyan Doshi
2025-03-30 12:18 ` Ramiro Polla
2025-03-30 12:12 ` Ramiro Polla
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=b8df6d89-2f93-5031-1b1c-1e1f2a141841@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