On 2015-02-20 06:43, Martin Jansa wrote:
On Thu, Feb 12, 2015 at 07:01:17PM -0700, Gary Thomas wrote:
On 2015-02-12 18:08, Martin Jansa wrote:
Does it have --enable-* options for the new PACKAGECONFIGs? If yes then it
should specify them as well (advantage at least in some projects is that
On Thu, Feb 12, 2015 at 07:01:17PM -0700, Gary Thomas wrote:
On 2015-02-12 18:08, Martin Jansa wrote:
Does it have --enable-* options for the new PACKAGECONFIGs? If yes then it
should specify them as well (advantage at least in some projects is that
when it explicitly asking for
foo and
On Fri, Feb 20, 2015 at 07:02:22AM -0700, Gary Thomas wrote:
On 2015-02-20 06:43, Martin Jansa wrote:
On Thu, Feb 12, 2015 at 07:01:17PM -0700, Gary Thomas wrote:
On 2015-02-12 18:08, Martin Jansa wrote:
Does it have --enable-* options for the new PACKAGECONFIGs? If yes then
it should
On 2015-02-20 07:34, Martin Jansa wrote:
On Fri, Feb 20, 2015 at 07:02:22AM -0700, Gary Thomas wrote:
On 2015-02-20 06:43, Martin Jansa wrote:
On Thu, Feb 12, 2015 at 07:01:17PM -0700, Gary Thomas wrote:
On 2015-02-12 18:08, Martin Jansa wrote:
Does it have --enable-* options for the new
mplayer2 no longer needs to be blacklisted as OE-core has moved
to libav_9.16.
[v2-v3] Also update build dependencies to quash QA warnings, using
PACKAGECONFIG for most optional features.
Signed-off-by: Gary Thomas g...@mlbassoc.com
---
meta-oe/recipes-multimedia/mplayer/mplayer2_git.bb | 9
Does it have --enable-* options for the new PACKAGECONFIGs? If yes then it
should specify them as well (advantage at least in some projects is that
when it explicitly asking for foo and foo is unusable it will end with
fatal error instead of ignoring broken foo dependency.
On Fri, Feb 13, 2015 at
On 2015-02-12 18:08, Martin Jansa wrote:
Does it have --enable-* options for the new PACKAGECONFIGs? If yes then it
should specify them as well (advantage at least in some projects is that when
it explicitly asking for
foo and foo is unusable it will end with fatal error instead of ignoring
