From: Hendrik Leppkes <h.leppkes@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH]configure: Assume target-os=win32 for toolchain msvc
Date: Tue, 13 Dec 2022 20:21:32 +0100
Message-ID: <CA+anqdwFJ2p=By7ZXOa-GoLqY-zyamdvrX1=1Tw44W3-mDG1Eg@mail.gmail.com> (raw)
In-Reply-To: <CAB0OVGqczEsFpCrvKd7sk+Kiq51G__KwQYZ+1QnJMg2NQh4NWA@mail.gmail.com>
On Tue, Dec 13, 2022 at 8:02 PM Carl Eugen Hoyos <ceffmpeg@gmail.com> wrote:
>
> Am So., 27. Nov. 2022 um 18:42 Uhr schrieb Carl Eugen Hoyos
> <ceffmpeg@gmail.com>:
> >
> > Am So., 27. Nov. 2022 um 18:16 Uhr schrieb Hendrik Leppkes
> > <h.leppkes@gmail.com>:
> > >
> > > On Sun, Nov 27, 2022 at 6:13 PM Carl Eugen Hoyos <ceffmpeg@gmail.com> wrote:
> > > >
> > > > Hi!
> > > >
> > > > Attached patch slightly simplifies building with MSVC.
> > > >
> > > > Please comment, Carl Eugen
> > >
> > > I don't think any toolchain value should make assumptions about the
> > > host it is running on, because between WSL and Wine, you can certainly
> > > do a bunch of specific things where this is not true.
> >
> > If this is true, then my patch is of course incorrect.
> > But could you give an example?
> > I was under the impression that cl.exe can only run
> > in win32.
>
> Ping.
> Could you give an example where host-os is not win32 when
> compiling with msvc?
>
When using wine, your host is linux.
- Hendrik
_______________________________________________
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-12-13 19:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 17:05 Carl Eugen Hoyos
2022-11-27 17:16 ` Hendrik Leppkes
2022-11-27 17:42 ` Carl Eugen Hoyos
2022-12-13 19:00 ` Carl Eugen Hoyos
2022-12-13 19:21 ` Hendrik Leppkes [this message]
2022-12-13 21:51 ` Carl Eugen Hoyos
2022-12-13 23:43 ` Timo Rothenpieler
2022-12-14 10:55 ` Carl Eugen Hoyos
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='CA+anqdwFJ2p=By7ZXOa-GoLqY-zyamdvrX1=1Tw44W3-mDG1Eg@mail.gmail.com' \
--to=h.leppkes@gmail.com \
--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