[Buildroot] Chromium v7 test

Fame Castle famecastle at gmail.com
Wed Sep 11 16:57:37 UTC 2019

Hi Thomas,
it's great to see your interest in this. If I can help you in
any way, please let me know. I'm still interested in this as a long term
goal, while I'm working on different projects now. I would however
appreciate any progress with this.

I think the following is interesting:
I am using CEF with Python (called cefpython). I install it using the
Python Package Manager pip and then on my host machine I got a folder with
cef browser binaries somewhere. I just took those binaries and the Python
bindings and copied them into my Buildroot-OS. Then, I was actually able to
get my Python CEF application working. It went fluently! So at its core,
this should be really possible. However, this doesn't feel like a nice
implementation. And, some other window management libraries which theirself
take CEF and enable you to control the application window, failed with
Segmentation faults. I'm confident this may be due to the usage of my
host's binaries. But I think it's interesting that it worked. So we should
find our way and make successfull Chromium builds.

I hope you have good success with this. All the best,
~ Fame(castle)

On Wed, Sep 11, 2019 at 6:50 PM Thomas Preston <
thomas.preston at codethink.co.uk> wrote:

> Hi,
> Thanks for getting back to us so quickly.
> On 11/09/2019 17:29, Joseph Kogut wrote:
> > On Wed, Sep 11, 2019 at 3:24 AM Thomas Preston
> > <thomas.preston at codethink.co.uk> wrote:
> >> Sorry to resurrect this old thread! We're in the process of creating a
> >> buildroot package for CEF [0] and the work you've done on this Chromium
> package
> >> is interesting!
> >
> > No problem. This is an interesting area, and I'd be glad to see some
> > Chromium based packages and applications added. Part of my motivation
> > for creating a Chromium package was actually to add CEF at some point.
> Okay great. Our original strategy was to have the CEF package depend on the
> Chromium package but as it turns out, CEF modifies the Chromium source,
> then
> relies heavily on the Chromium build system. This isn't something which
> buildroot really supports, so we're just downloading the Chromium tarball
> in
> the CEF package, using the _EXTRA_DOWNLOADS makefile variable.
> This might change as we discover more though...
> >> @Joseph, I noticed that you removed the `bootstrap.py` stage and
> referenced
> >> `gn` directly (rather than `out/Release/gn`) in your patch to build
> Chromium
> >> v75 [2]. Is gn on your path somehow? I'm not sure if this WIP patch is
> supposed
> >> to work yet :)
> >
> > Right. It's been a while since I've worked on this branch, but I would
> > assume that gn is being found on my system path here. I think my
> > intention was to add it as a package at some point. Anyway, the WIP
> > branch isn't supposed to work yet, which is why I haven't submitted
> > it.
> Okay got it. There seems to be a copy of gn bundled in with the Chromium
> tarball
> at buildtools/linux64/gn, which is what the depot_tools/gn script searches
> for
> anyway - so we're just using that for now. We /think/ we can get away
> without
> using depot_tools.
> > Thanks for starting the work on this, and I'm happy to contribute
> > however I can. If you push your work to a public repository, I'd be
> > happy to look it over, and you can CC me on any patches you send to
> > the mailing list.
> Will do, much appreciated! There's nothing stopping us from working in the
> open
> so we'll get patches out as soon as we can.
> Tom
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20190911/4da0f6c7/attachment-0002.html>

More information about the buildroot mailing list