All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@ossystems.com.br>
To: OpenEmbedded Devel List <openembedded-devel@lists.openembedded.org>
Cc: pnandyala <Pavan.Nandyala@lnttechservices.com>,
	Zoltan Kuscsik <zoltan.kuscsik@linaro.org>,
	knagabhirava <kalyankumar.nagabhirava@lnttechservices.com>
Subject: Re: meta-browser][PATCH V2] cef3: Add recipe for Chromium Embedded Framework
Date: Tue, 24 Mar 2015 08:56:25 -0300	[thread overview]
Message-ID: <CAP9ODKoFdepGX7OZu8XxMQVr-ssUCG_Ndyyj6GROOACViiMhEw@mail.gmail.com> (raw)
In-Reply-To: <CAMKF1sqm5ARrWih-TgnzFXgEGXR97o=iUU_xR-fvp_bLC=SyEQ@mail.gmail.com>

On Tue, Mar 24, 2015 at 12:01 AM, Khem Raj <raj.khem@gmail.com> wrote:
> On Mon, Mar 23, 2015 at 1:00 PM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
>>
>> Couldn't it reuse the Chromium recipe we use?
>
> Surely and I have thought that for as second iteration after its soaked in
> Right now they use different versions of chromium so there are some
> issues around.
> this will also mean some changes in chromium recipes.

I'd prefer to do it once and avoid adding another recipe and handle
same problems we had solved there. Also this allows for example the
use of i.MX patches on meta-fsl-arm.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750


  reply	other threads:[~2015-03-24 11:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-22 17:28 meta-browser][PATCH V2] cef3: Add recipe for Chromium Embedded Framework Khem Raj
2015-03-23 20:00 ` Otavio Salvador
2015-03-24  3:01   ` Khem Raj
2015-03-24 11:56     ` Otavio Salvador [this message]
2015-03-24 15:51       ` Khem Raj
2015-03-24 16:36         ` Otavio Salvador
2015-03-24 18:51           ` Khem Raj
2015-03-24 18:58             ` Otavio Salvador
2015-04-27 10:53               ` Alex J Lennon

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=CAP9ODKoFdepGX7OZu8XxMQVr-ssUCG_Ndyyj6GROOACViiMhEw@mail.gmail.com \
    --to=otavio@ossystems.com.br \
    --cc=Pavan.Nandyala@lnttechservices.com \
    --cc=kalyankumar.nagabhirava@lnttechservices.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=zoltan.kuscsik@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.