All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: openembedded-devel@lists.openembedded.org,
	 pnandyala <Pavan.Nandyala@lnttechservices.com>,
	Zoltan Kuscsik <zoltan.kuscsik@linaro.org>
Cc: knagabhirava <kalyankumar.nagabhirava@lnttechservices.com>
Subject: Re: meta-browser][PATCH V2] cef3: Add recipe for Chromium Embedded Framework
Date: Mon, 27 Apr 2015 12:53:35 +0200	[thread overview]
Message-ID: <553E152F.6090601@dynamicdevices.co.uk> (raw)
In-Reply-To: <CAP9ODKrrABT39MyQUYqnZY3BRkvM_amzV8mjaVQRwMvhpQGtuw@mail.gmail.com>



On 24/03/2015 19:58, Otavio Salvador wrote:
> 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.
>

Hi - thanks for the initial cef3 recipe. I've been taking a look at this
with a view to a cef3 recipe based on chromium.inc that I can use to
build for i.MX6 (the original recipe was failing to build for me)

I have this building now and was able to run cefsimple on i.MX6 although
I am unsure whether it's correctly using hardware acceleration and I
think it needs more work / cleanups.

I wish to use cefglue to wrap a Mono WebBrowser control around CEF3 and
there are a set of standard Chromium builds it supports to this end.

I can build Chromium 39.0.2171.95 and the current 40.0.2214.91 recipe
but when I go to 41.0.2272.104 which is supported by one of the newer
cefglue releases I get an error of this form:

| In file included from ../../v8/src/base/sys-info.cc:19:0:
| /usr/include/c++/4.8/limits:42:28: fatal error: bits/c++config.h: No
such file or directory
|  #include <bits/c++config.h>
|                             ^
| compilation terminated.
| ninja: build stopped: subcommand failed.

I'm using a fairly vanilla x64 Ubuntu 14.04.2 LTS. It looks like some
kind of paths/sysroot issue with the host compiler settings. I see
googling that others have had similar issues with x64 hosts  but I can't
quite work out what to do.

Can anybody advise?

Thanks,

Alex


      reply	other threads:[~2015-04-27 10:59 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
2015-04-27 10:53               ` Alex J Lennon [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=553E152F.6090601@dynamicdevices.co.uk \
    --to=ajlennon@dynamicdevices.co.uk \
    --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.