Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Carlos Alberto Lopez Perez <clopez@igalia.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-browser][PATCH 3/3] chromium: Rework the evaluation of the Wayland feature.
Date: Wed, 16 Sep 2015 16:08:36 +0200	[thread overview]
Message-ID: <55F977E4.3030202@igalia.com> (raw)
In-Reply-To: <CAMKF1sqRmW0WYzAyusDEW47onz-h9W0tZ-sYWyqp28=u3fbzgQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 423 bytes --]

On 15/09/15 18:56, Khem Raj wrote:
> On Tue, Sep 15, 2015 at 5:50 AM, Carlos Alberto Lopez Perez
> <clopez@igalia.com> wrote:
>> +    CHROMIUM_BUILD_TYPE = d.getVar('CHROMIUM_BUILD_TYPE', True)
> 
> Lets default to one if its not set by user and set a bb.note about
> what is chosen may be Release as default is good.
> 

It already defaults to Release. The first patch in the series does that
in chromium.inc


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

  reply	other threads:[~2015-09-16 14:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-15 12:49 [meta-browser][PATCH 0/3] chromium: make the build type configurable Carlos Alberto Lopez Perez
2015-09-15 12:50 ` [meta-browser][PATCH 1/3] chromium: Allow to build in Debug mode Carlos Alberto Lopez Perez
2015-09-15 15:03   ` Trevor Woerner
2015-09-15 17:00     ` Khem Raj
2015-09-16 14:07       ` Carlos Alberto Lopez Perez
2015-09-15 12:50 ` [meta-browser][PATCH 2/3] chromium: Clean the definitions of some ozone-wayland variables Carlos Alberto Lopez Perez
2015-09-15 12:50 ` [meta-browser][PATCH 3/3] chromium: Rework the evaluation of the Wayland feature Carlos Alberto Lopez Perez
2015-09-15 16:56   ` Khem Raj
2015-09-16 14:08     ` Carlos Alberto Lopez Perez [this message]
2015-09-16 20:14       ` Khem Raj

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=55F977E4.3030202@igalia.com \
    --to=clopez@igalia.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