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 15:58:00 -0300	[thread overview]
Message-ID: <CAP9ODKrrABT39MyQUYqnZY3BRkvM_amzV8mjaVQRwMvhpQGtuw@mail.gmail.com> (raw)
In-Reply-To: <CAMKF1sqf=txyROy9rQ0qyPgD5iM+YV358X3-Z3kVmCrg1t+U+w@mail.gmail.com>

On Tue, Mar 24, 2015 at 3:51 PM, Khem Raj <raj.khem@gmail.com> wrote:
> On Mar 24, 2015 9:36 AM, "Otavio Salvador" <otavio@ossystems.com.br> wrote:
>>
>> On Tue, Mar 24, 2015 at 12:51 PM, Khem Raj <raj.khem@gmail.com> wrote:
>> >
>> >> On Mar 24, 2015, at 4:56 AM, Otavio Salvador <otavio@ossystems.com.br>
> wrote:
>> >>
>> >>
>> >> 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.
>> >
>> > My usecase is not i.MX moreover I do not have i.MX h/w to test as well,
> current set work fine for the architectures I need it for, if someone wants
> to help in testing on other machines, its welcome. however as I said, it
> will be in subsequent work to unite both recipes due to the overhead as
> explained in last email.
>>
>> I am not asking you to test cef3 on i.MX, this is fine. I don't want
>> another giant build recipe with duplication.
>
> I am aware of that. This let's other folks hands on it with a working
> version. Moving cef to latest chromium is a bigger exercise and will delay
> this. That's the motivation.

Reuse chromium.inc file for this, so we at least avoid recipe
duplication? If you have a good reason to avoid it I am fine but I
certainly prefer reuse here.

-- 
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 18:57 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
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 [this message]
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=CAP9ODKrrABT39MyQUYqnZY3BRkvM_amzV8mjaVQRwMvhpQGtuw@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.