[FFmpeg-devel] [MSVC toolchain] Patch to allow building FFmpeg with Linux bash on Windows (WSL)
Carl Eugen Hoyos
ceffmpeg at gmail.com
Wed Apr 24 02:38:47 EEST 2019
2017-12-29 13:16 GMT+01:00, Cyber Sinh <cyber.sinh at free.fr>:
> Sorry for the diff instead of regular git patch. Here is the patch.
Only saw this today after wondering
why nobody tried using wsl before...
How can I test this part of the patch?
In which situation is it supposed to make a difference?
diff --git a/compat/windows/mslink b/compat/windows/mslink
index 07b2b3e378..9b6b83c4ed 100755
@@ -1,9 +1,9 @@
-LINK_EXE_PATH=$(dirname "$(command -v cl)")/link
+LINK_EXE_PATH=$(dirname "$(command -v cl.exe)")/link.exe
if [ -x "$LINK_EXE_PATH" ]; then
I will apply the makedef part that I just tested successfully.
> -----Message d'origine-----
> De : ffmpeg-devel [mailto:ffmpeg-devel-bounces at ffmpeg.org] De la part de
> Envoyé : vendredi 29 décembre 2017 12:54
> À : ffmpeg-devel at ffmpeg.org
> Objet : Re: [FFmpeg-devel] [MSVC toolchain] Patch to allow building FFmpeg
> with Linux bash on Windows (WSL)
> On Fri, 29 Dec 2017 10:44:21 +0100
> Hendrik Leppkes <h.leppkes at gmail.com> wrote:
>> On Fri, Dec 29, 2017 at 3:43 AM, Cyber Sinh <cyber.sinh at free.fr> wrote:
>> > The attached patch changes the configure script for FFmpeg (and
>> > associated shell scripts) to call MSVC tools including their
>> > extensions (cl.exe instead of cl for example). This is necessary,
>> > because WSL can automatically launch Windows processes from the
>> > Linux side but only if the process is in the path and includes the
>> > full name. Linux doesn't automatically append .exe and such to invoke a
>> > file.
>> The attached file is corrupted. Please ensure its in git format-patch
>> format. As it is, I can't even read it at all.
> It's in UTF-16, and just a diff. Yeah, nobody can comfortably read it.
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
More information about the ffmpeg-devel