On 21 February 2016 at 22:44, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> I'd note that if we had a way to know if a recipe was really autotools
> or just acts a bit like it, it would help a lot...
>
Something I've been meaning to do for a long time is review everything that
is
On Sun, 2016-02-21 at 11:47 +0100, Martin Jansa wrote:
> What's the advantage of more global .inc file?
In OE-Core it started as a standalone experiment which made sense as a
separate .inc as we've done with some other things of this nature. I
thought it was going to take longer to work through
What's the advantage of more global .inc file?
IMHO it's only increasing chances for conflicts when merging/cherry-picking.
On Sun, Feb 21, 2016 at 11:30 AM, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Thu, 2016-02-18 at 20:43 +, Christopher Larson wrote:
> > I think
On Thu, 2016-02-18 at 20:43 +, Christopher Larson wrote:
> I think the convention is to add such workarounds to no-static
> -libs.inc,
> not the recipe, at this time.
This is a good question. I was just doing some world builds with meta
-oe in and have a few more of these fixes.
Referencing
On Thu, Feb 18, 2016 at 6:43 PM, Christopher Larson wrote:
> I think the convention is to add such workarounds to no-static-libs.inc,
> not the recipe, at this time.
For OE-Core, yes. For Meta-OE? I think the recipe is the easiest to
notice when doing the upgrade.
--
Otavio
I think the convention is to add such workarounds to no-static-libs.inc,
not the recipe, at this time.
On Thu, Feb 18, 2016 at 10:30 AM Fabio Berton
wrote:
> As of commit OE-Core:773c9e18071d71454473dd81aff911104a2e9bc6
> EXTRA_OECONF is appended with the option
As of commit OE-Core:773c9e18071d71454473dd81aff911104a2e9bc6
EXTRA_OECONF is appended with the option --disable-static on
DISABLE_STATIC variable and this cause the error:
DEBUG: Python function sysroot_cleansstate finished
DEBUG: Executing shell function do_configure
Bad option