Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Ziemowit Laski <zlaski@ziemas.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] mswindres: Use '-' instead of '/' for rc.exe options
Date: Thu, 9 Feb 2023 21:01:42 +0000
Message-ID: <BYAPR12MB323800473D370F5C06DC5213A4D99@BYAPR12MB3238.namprd12.prod.outlook.com> (raw)
In-Reply-To: <27182552-d0fb-fa0-d15-b969bdd09ada@martin.st>

> FWIW, this setup is definitely being used by lots of others already - so
> whenever there's such an issue, the main question to ask is why others
> haven't run into the issue before. But improvements are definitely
> welcome!

You have to have PATH set up so that rc.exe is found inside the Windows SDK.
This is NOT the default behavior.  Usually, you would have to invoke the
'Developer Command Prompt' from the start menu to get the correct environment.

But I have my system set up so that the Microsoft tools are ALWAYS found,
regardless of which shell you are running.  That could explain the different
behavior that I'm seeing.

> You should probably talk about the option '/nologo' here, there's no
> '/logo' option afaik.

Yes, good catch, thanks.

> 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.

> Anyway, with the commit message fixed, and the case of /? changed into -?,
> this patch would seem fine to me - thanks for your contribution!

Will do.  Thanks for your review. 😊

--Zem
_______________________________________________
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:[~2023-02-09 21:02 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 [this message]
2023-02-09 21:59     ` Hendrik Leppkes
2023-02-09 22:14     ` Martin Storsjö
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=BYAPR12MB323800473D370F5C06DC5213A4D99@BYAPR12MB3238.namprd12.prod.outlook.com \
    --to=zlaski@ziemas.net \
    --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