<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body><div><div style="font-family: Calibri,sans-serif; font-size: 11pt;">I wasn't aware of that ability of msys now.<br><br>Even so, for the sake of one lib of code is it not worth doing it for those who prefer Cygwin?<br><br>I obviously can't force you to include it though.<br><br>Phil</div></div><div dir="ltr"><hr><span style="font-family: Calibri,sans-serif; font-size: 11pt; font-weight: bold;">From: </span><span style="font-family: Calibri,sans-serif; font-size: 11pt;"><a href="mailto:qyot27@gmail.com">Stephen Hutchinson</a></span><br><span style="font-family: Calibri,sans-serif; font-size: 11pt; font-weight: bold;">Sent: </span><span style="font-family: Calibri,sans-serif; font-size: 11pt;">05/11/2015 03:46</span><br><span style="font-family: Calibri,sans-serif; font-size: 11pt; font-weight: bold;">To: </span><span style="font-family: Calibri,sans-serif; font-size: 11pt;"><a href="mailto:x265-devel@videolan.org">Development for x265</a></span><br><span style="font-family: Calibri,sans-serif; font-size: 11pt; font-weight: bold;">Subject: </span><span style="font-family: Calibri,sans-serif; font-size: 11pt;">Re: [x265] Building on Cygwin</span><br><br></div>On 11/4/2015 7:29 PM, Phil Rosenberg wrote:<br>> The advantage of Cygwin when building open source code is having<br>> access to a package manager and Linux-like environment. So in my case<br>> when building ffmpeg with a number of additional dependencies I could<br>> install most dependencies with the package manager and easily build<br>> the rest then build ffmpeg using standard the standard ./configure,<br>> make, make install. This was an order of magnitude easier than trying<br>> to build via visual studio (which I ordinarily prefer) and<br>> significantly easier than having to build all the dependancies (and<br>> their dependancies...) with MinGW.<br>The package management argument doesn't hold up anymore,<br>considering the advent of msys2 a couple years ago. Even uses<br>a Windows port of Arch Linux's pacman to do it.<br><br>And as far as I'm aware, FFmpeg hasn't added *.vcxproj or *.sln<br>files, so compiling it with Visual Studio still requires entering<br>an MSys(2) environment (maybe just entering the Bourne shell)<br>from the VS Command Prompt and then using --toolchain=msvc<br>during ./configure. So even at that, msys2 should have you<br>covered on the deps front.<br>_______________________________________________<br>x265-devel mailing list<br>x265-devel@videolan.org<br>https://mailman.videolan.org/listinfo/x265-devel<br></body></html>