<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;">Hi Neeptha. That would be great. Just feel free to commit locally.<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:deepthi@multicorewareinc.com">Deepthi Nandakumar</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 07:06</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><div dir="ltr"><div>Your cygwin patch can be pushed, but the x265 team will not document/test Cygwin support and functionality. We don't want to push you to a new build environment for this fairly trivial change.<br><br></div>Would you like to send a CLA, or we'll just commit it locally?<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Nov 5, 2015 at 12:27 PM, Phil Rosenberg <span dir="ltr"><<a href="mailto:p.d.rosenberg@gmail.com" target="_blank">p.d.rosenberg@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; padding-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px; border-left-style: solid;"><div><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" target="_blank">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><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" target="_blank">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></span></div><div><div class="h5">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><a href="mailto:x265-devel@videolan.org" target="_blank">x265-devel@videolan.org</a><br><a href="https://mailman.videolan.org/listinfo/x265-devel" target="_blank">https://mailman.videolan.org/listinfo/x265-devel</a><br></div></div></div><br>_______________________________________________<br>
x265-devel mailing list<br>
<a href="mailto:x265-devel@videolan.org">x265-devel@videolan.org</a><br>
<a href="https://mailman.videolan.org/listinfo/x265-devel" target="_blank" rel="noreferrer">https://mailman.videolan.org/listinfo/x265-devel</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div><div>Deepthi Nandakumar<br></div>Engineering Manager, x265<br></div>Multicoreware, Inc<br></div></div>
</div>
</body></html>