From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] configure: Fix Microsoft tools detection
Date: Thu, 3 Feb 2022 14:33:05 +0200 (EET)
Message-ID: <8bc3ae4-691a-73ac-df30-17ed50a3c457@martin.st> (raw)
In-Reply-To: <86DF9578-5EB0-4773-B37D-1A8A43A57CC4@gmail.com>
On Thu, 3 Feb 2022, Marvin Scholz wrote:
>
>
> On 3 Feb 2022, at 12:55, Hendrik Leppkes wrote:
>
>> On Thu, Feb 3, 2022 at 12:34 PM Martin Storsjö <martin@martin.st>
>> wrote:
>>>
>>> I remember that there has been some variance throughout the versions
>>> for
>>> exactly what MSVC prints as the identification thoughout the
>>> versions, but
>>> I think 'Microsoft.*Optimizing.*Compiler' should be safe.
>>>
>>
>> I was wondering if non-english locale would translate that string, but
>> I can't easily test that, I don't think.
>>
>
> Sorry, need to correct myself. It is indeed localized I was just lacking
> the language pack…
>
> For example in german it is:
>
> Microsoft (R) C/C++-Optimierungscompiler Version 19.30.30709 für x64
> Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.
Oh, thanks for that!
I presume that this also could break the other existing check for armasm
too? If you run e.g. "vsdevcmd -host_arch=x64 -arch=arm64" and then
"armasm64", what does that print?
// 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:[~2022-02-03 12:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 20:13 Kacper Michajłow
2022-01-26 14:00 ` Martin Storsjö
2022-02-03 6:44 ` Kacper Michajlow
2022-02-03 11:34 ` Martin Storsjö
2022-02-03 11:55 ` Hendrik Leppkes
2022-02-03 12:08 ` Marvin Scholz
2022-02-03 12:26 ` Marvin Scholz
2022-02-03 12:33 ` Martin Storsjö [this message]
2022-02-03 12:43 ` Marvin Scholz
2022-02-03 12:47 ` Martin Storsjö
2022-02-03 16:02 ` Marvin Scholz
2022-02-07 21:00 ` 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=8bc3ae4-691a-73ac-df30-17ed50a3c457@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