Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-browser] New chromium warnings
Date: Tue, 30 Jun 2015 13:14:37 -0600	[thread overview]
Message-ID: <5592EA9D.2070902@mlbassoc.com> (raw)
In-Reply-To: <CAJTo0LYWCvG9oog=GwVMjqEB2RM_zAT_Vr8zO2tX=9WeKbdPXQ@mail.gmail.com>

On 2015-06-30 13:10, Burton, Ross wrote:
> On 30 June 2015 at 16:46, Gary Thomas <gary@mlbassoc.com> wrote:
>
>> They are coming from
>> meta-fsl-arm/browser-layer/recipes-browser/chromium/chromium-imx.inc
>> and my local.conf.  The chromium recipe checks the PACKAGECONFIG variable
>> for these settings, but is not using PACKAGECONFIG the normal way.  It's
>> just the warnings that are new.
>>
>> I suspect the chromium recipe(s) need to be rewritten to play nice
>> with PACKAGECONFIG...
>>
>
> I'm pleased we've got the warning, but recipes that are using a
> PACKAGECONFIG variable to configure stuff but then not actually using the
> PACKAGECONFIG machinery now need to add stub definitions for each of the
> flags they're using:
>
> PACKAGECONFIG[use-gl] = ""
> etc
>

As I expected.  I'll send a patch for this.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


      reply	other threads:[~2015-06-30 19:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30 15:09 [meta-browser] New chromium warnings Gary Thomas
2015-06-30 15:32 ` Burton, Ross
2015-06-30 15:46   ` Gary Thomas
2015-06-30 19:10     ` Burton, Ross
2015-06-30 19:14       ` Gary Thomas [this message]

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=5592EA9D.2070902@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=openembedded-devel@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