[OE-core] dropping commerical flags in mpg123 and lame recipes

The lame and mpg123 can be built only if the commercial flag is whitelisted. However, the remaining mp3 patents expired in December, and no more royalties exist. This is why in GStreamer, the mpg123 and lame plugins were moved from -ugly to -good. So, can we drop the commercial flag in

Re: [OE-core] kernel menuconfig broken?

On Fri, 13 Apr 2018 00:12:16 +0200 Andreas Müller wrote: > On Thu, Apr 12, 2018 at 11:46 PM, Andreas Müller > wrote: > > On Thu, Apr 12, 2018 at 11:38 PM, Cal Sullivan > > wrote: > >> If you're using a

[OE-core] [PATCH] run-postinsts: Replace pi_dir variable test

Since commit 5159ddcb62682e1b7e63a20a9218ea96e3fe10a2 string length test performed against pi_dir has effectively never been able to succeed. Change this to rather test if pi_dir is not an existing directory. By doing we remove the chance of seeing the following console error message during first

Re: [OE-core] dropping commerical flags in mpg123 and lame recipes

On Sat, Apr 14, 2018 at 1:30 AM, Carlos Rafael Giani wrote: > The lame and mpg123 can be built only if the commercial flag is whitelisted. > > However, the remaining mp3 patents expired in December, and no more > royalties exist. This is why in GStreamer, the mpg123 and

Re: [OE-core] kernel menuconfig broken?

On Sat, Apr 14, 2018 at 11:10 AM, Paul Barker wrote: > On Fri, 13 Apr 2018 00:12:16 +0200 > Andreas Müller wrote: > >> On Thu, Apr 12, 2018 at 11:46 PM, Andreas Müller >> wrote: >> > On Thu, Apr 12, 2018 at 11:38 PM, Cal

[OE-core] Custom progress handlers

Hello all, I have implemented a simple custom progress handler in bitbake/lib/bb/progress.py. It's designed to handle bar-style progress. To use it for my shell tasks, I have modified "exec_func_shell" in bitbake/lib/bb/build.py. It's implemented as a new value for the "progress" varflag. Is

Re: [OE-core] Custom progress handlers

On Sat, Apr 14, 2018 at 11:56 AM, Chris Laplante via Openembedded-core wrote: > I have implemented a simple custom progress handler in > bitbake/lib/bb/progress.py. It’s designed to handle bar-style progress. To > use it for my shell tasks, I have

Re: [OE-core] kernel menuconfig broken?

If everyone else is seeing issues, it makes me wonder why it's working perfectly fine for me! -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] kernel menuconfig broken?

On Sat, Apr 14, 2018 at 8:42 PM, Trevor Woerner wrote: > If everyone else is seeing issues, it makes me wonder why it's working > perfectly fine for me! > Seems you have ncurses installed on horst that matches oe's native ncurses. The patch description [1] gives details. [1]

Re: [OE-core] Custom progress handlers

Great, I'll give it a go then :) The type of progress output I'm handling is that of a fixed-width bar that fills up with a certain character (e.g. '*' or '#"). Just like BitBake's own output. Moreover I want to generalize it to support multiple weighted stages, e.g.: STAGE 1: message

Re: [OE-core] [Openembedded-architecture] LAYERSERIES

On Fri 2018-04-06 @ 10:56:53 PM, Richard Purdie wrote: > To be really clear, "master" is never a value that would appear in > LAYERSERIES. That would let everyone be lazy and master would match > everywhere, then this would all be pointless. So what happens when the master branch of a BSP layer