Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 401] New: new package: ffmpeg
Date: Mon, 15 Jun 2009 11:26:42 +0000 (UTC)	[thread overview]
Message-ID: <bug-401-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=401

           Summary: new package: ffmpeg
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: s.neumann at raumfeld.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created an attachment (id=401)
 --> (https://bugs.busybox.net/attachment.cgi?id=401)
package/multimedia/ffmpeg/Config.in

FFmpeg is a complete, cross-platform solution to record, convert and stream
audio and video. See http://ffmpeg.org/

I am attaching Config.in and ffmpeg.mk to add ffmpeg as a new package to
buildroot. So far the buildroot this package only builds libavcodec and
libavformat. Support for the ffmpeg, ffplay and ffserver binaries could be
added later. Another thing that could, and probably should, be added is a way
to easily configure the set of supported codecs from the buildroot config
system. But to keep things simple, here's a simple package definition to start
with.


-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2009-06-15 11:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15 11:26 bugzilla at busybox.net [this message]
2009-06-15 11:27 ` [Buildroot] [Bug 401] new package: ffmpeg bugzilla at busybox.net
2010-02-21 22:32 ` bugzilla at busybox.net
2010-06-15  6:53 ` bugzilla at busybox.net

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=bug-401-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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