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: Mon, 13 Feb 2023 00:25:36 +0200 (EET) Message-ID: <8bac6311-d03c-d20-f1f1-ecb3c5b937af@martin.st> (raw) In-Reply-To: <BYAPR12MB3238F9F90E2CFD71853FCFF1A4DE9@BYAPR12MB3238.namprd12.prod.outlook.com> On Sat, 11 Feb 2023, Ziemowit Laski wrote: > Thanks for the detailed explanation. Now my head hurts. > > I guess by "native" you mean those apps that do not depend on MSYS/Cygwin > DLL functionality? All of the apps are native. Yeah, more or less. They use the regular win32 api just like MSVC based apps do. > So I can definitely understand the appeal of MinGW. But what about > MSYS? Is it some sort of copyright/GPL avoidance scheme? Not at all - it's entirely a technical thing. MSYS, which is a fork of cygwin, is an environment to provide a full POSIX (i.e. unix) environment on top of Windows, which involves a lot of trickery to make system calls like fork() work on top of a OS that doesn't provide that. MSYS apps generally don't use/see the win32 API at all (when building MSYS/Cygwin code, the '_WIN32' define isn't set), they believe they're running on top of any regular unix, more or less. GCC can run on plain win32 thanks to mingw, it doesn't use any fancy POSIX APIs, but e.g. bash doesn't run on mingw/win32 since it uses so many unix specific concepts that don't exist on win32. That is - it's "easier" (or more wisely spent effort) to just try to emulate unix concepts in a full emulation layer, than to port bash (and other similar tools) to work directly on win32. // 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-12 22:25 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ö 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ö [this message] 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=8bac6311-d03c-d20-f1f1-ecb3c5b937af@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