From: wynfield@gmail.com
To: <cygwin@cygwin.com>
Subject: Re: Audio coding/encoding conversions
Date: Mon, 17 Dec 2007 00:40:00 -0000 [thread overview]
Message-ID: <20071217094028.3780@blackhawk> (raw)
In-Reply-To: Your message of Thu, 13 Dec 2007 21:33:31 +0000 (UTC) <loom.20071213T212259-92@post.gmane.org>
Thanks Victor and Dave, for the information regarding ffmpeg, both about the future of it for cygwin and how to get by for now.
Regards,
Wynfield
----------------
Victor Paesa <wzrlpy@arsystel.com> wrote:
> Hi,
>
> Dave Korn writes:
> >
> > On 13 December 2007 12:46, Wynfield Henman wrote:
> >
> > > Has anybody had any success building --> ffmpeg
> > > on cygwin. It has a rich set of codecs it can convert to and from.
> >
> > ffmpeg requires an llrintf() implementation to compile. newlib doesn't
> > currently have one, but I'm in the process of sending a patch, so it might get
> > a lot easier once I've done that and there's a fresh cygwin snapshot been
> > generated.
>
> Until that very welcomed patch is applied, you may choose among three ways
> (not so correct) to get ffmpeg on cygwin:
>
> a) Inline llrintf()
> http://article.gmane.org/gmane.comp.video.ffmpeg.devel/37442
>
> b) Leverage MinGW's implementation:
> http://ffmpeg.mplayerhq.hu/general.html#SEC16
>
> c) Get the binaries from Cygwin Ports:
> http://cygwinports.dotsrc.org/
>
> Regards,
> Víctor
>
>
> --
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> Problem reports: http://cygwin.com/problems.html
> Documentation: http://cygwin.com/docs.html
> FAQ: http://cygwin.com/faq/
>
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
prev parent reply other threads:[~2007-12-17 0:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 12:45 Wynfield Henman
2007-12-13 12:53 ` Dave Korn
2007-12-13 21:34 ` Victor Paesa
2007-12-17 0:40 ` wynfield [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071217094028.3780@blackhawk \
--to=wynfield@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).