From: Derek Buitenhuis <derek.buitenhuis@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gstreamer: gst-ffmpeg: fix build issues for libav
Date: Sun, 05 Aug 2012 12:27:31 -0400 [thread overview]
Message-ID: <501E9EF3.2020208@gmail.com> (raw)
In-Reply-To: <EB05DE7F-A81E-4CF6-BD49-F93604EA1EDF@dominion.thruhere.net>
On 05/08/2012 7:52 AM, Koen Kooi wrote:
> I find it a lot easier to build gst-ffmpeg against an external libav, that way you don't have to jump through all these hoops to get a proper libav. That's what the meta-oe bbappend does :)
I've always wondered why Libav was not its own recipe. It seems like it
would be a lot easier to maintain... calling its configure from gst's
configure is... unpleasant. :)
- Derek
next prev parent reply other threads:[~2012-08-05 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 21:15 [PATCH] gstreamer: gst-ffmpeg: fix build issues for libav Yao Zhao
2012-08-04 18:57 ` Derek Buitenhuis
2012-08-05 11:52 ` Koen Kooi
2012-08-05 16:27 ` Derek Buitenhuis [this message]
2012-08-05 17:31 ` Koen Kooi
2012-08-05 19:11 ` Khem Raj
2012-08-05 22:16 ` Derek Buitenhuis
2012-08-07 15:24 ` Yao Zhao
2012-08-07 17:00 ` Derek Buitenhuis
2012-08-07 20:06 ` Derek Buitenhuis
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=501E9EF3.2020208@gmail.com \
--to=derek.buitenhuis@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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