From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] mswindres: Use '-' instead of '/' for rc.exe options
Date: Fri, 10 Feb 2023 00:14:49 +0200 (EET)
Message-ID: <4ecd356-f04b-afe0-6d17-ef9850d6df2@martin.st> (raw)
In-Reply-To: <BYAPR12MB323800473D370F5C06DC5213A4D99@BYAPR12MB3238.namprd12.prod.outlook.com>
On Thu, 9 Feb 2023, Ziemowit Laski wrote:
>> These changes seem fine, but you're apparently not touching the case at
>> the top, used for --version, where it is calling 'rc.exe /?'. For me, this
>
> That's an interesting point. I guess MinGW is "smart enough" not to rewrite
> "/?" because it doesn't represent a valid path to begin with. I will change
> it to "-?" as you suggest.
Just to clarify some details here - mingw doesn't do any such path
rewriting - that's all msys's doing. Mingw processes themselves are
entirely regular win32 processes which know nothing about unix style
paths; it's msys2 which does the whole unix-style paths and which
automatically tries to rewrite command line arguments as if they were
paths, with some level of heuristics.
Git bash also uses the msys2 layer, but apparently it uses a different
version of the msys2 runtime, since it didn't seem to fail when executing
"rc.exe /?", while the current msys2 version fails.
None of that has anything to do with mingw.
// 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:[~2023-02-09 22:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 19:52 Ziemowit Laski
2023-02-09 11:08 ` Martin Storsjö
2023-02-09 21:01 ` Ziemowit Laski
2023-02-09 21:59 ` Hendrik Leppkes
2023-02-09 22:14 ` Martin Storsjö [this message]
2023-02-10 1:47 ` Ziemowit Laski
2023-02-10 22:22 ` Martin Storsjö
2023-02-11 0:13 ` Ziemowit Laski
2023-02-12 22:25 ` Martin Storsjö
2023-02-13 5:17 ` Ziemowit Laski
2023-02-13 7:36 ` Martin Storsjö
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=4ecd356-f04b-afe0-6d17-ef9850d6df2@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