[x265] Building on Cygwin

[Phil Rosenberg]

I wasn't aware of that ability of msys now.

Even so, for the sake of one lib of code is it not worth doing it for those who prefer Cygwin?

I obviously can't force you to include it though.

Phil

-----Original Message-----
From: "Stephen Hutchinson" <qyot27 at gmail.com>
Sent: ‎05/‎11/‎2015 03:46
To: "Development for x265" <x265-devel at videolan.org>
Subject: Re: [x265] Building on Cygwin

On 11/4/2015 7:29 PM, Phil Rosenberg wrote:
> The advantage of Cygwin when building open source code is having
> access to a package manager and Linux-like environment. So in my case
> when building ffmpeg with a number of additional dependencies I could
> install most dependencies with the package manager and easily build
> the rest then build ffmpeg using standard the standard ./configure,
> make, make install. This was an order of magnitude easier than trying
> to build via visual studio (which I ordinarily prefer) and
> significantly easier than having to build all the dependancies (and
> their dependancies...) with MinGW.
The package management argument doesn't hold up anymore,
considering the advent of msys2 a couple years ago.  Even uses
a Windows port of Arch Linux's pacman to do it.

And as far as I'm aware, FFmpeg hasn't added *.vcxproj or *.sln
files, so compiling it with Visual Studio still requires entering
an MSys(2) environment (maybe just entering the Bourne shell)
from the VS Command Prompt and then using --toolchain=msvc
during ./configure.  So even at that, msys2 should have you
covered on the deps front.
_______________________________________________
x265-devel mailing list
x265-devel at videolan.org
https://mailman.videolan.org/listinfo/x265-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/x265-devel/attachments/20151105/7526ac41/attachment.html>