This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: libav or ffmpeg and associated tools
- From: David Stacey <drstacey at tiscali dot co dot uk>
- To: cygwin at cygwin dot com
- Date: Mon, 20 Jun 2016 19:29:44 +0100
- Subject: Re: libav or ffmpeg and associated tools
- Authentication-results: sourceware.org; auth=none
- References: <CAKw7uVhwxwr3Jd-JUCbzAXDSn3RSAoXJcrL8gV4ivw-qhK9Fcg at mail dot gmail dot com> <c5909e1b-d916-5f81-be83-a910f66d2c27 at gmail dot com> <1213779c-ed16-3ff1-5506-9e9ac48b00ec at tiscali dot co dot uk> <CAPsu6LiGCmJ_smRGjRXXE=n77hvU87410RV0XSv_yPH8QRa9ug at mail dot gmail dot com>
On 19/06/16 22:51, Brian Mathis wrote:
Is there any reason not to use the native Windows build instead? What
does the cygwin port gain you over that?
Other that the obvious difference of Windows and POSIX paths, there will
be differences in the way the two versions of ffmpeg are built. This
means that two builds of ffmpeg may well support different sets of file
formats. For each, try:
ffmpeg -codecs
ffmpeg -formats
and see which build best meets your needs.
Dave.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple