search

zoltan-ongithub / chromiumembedded

The Chromium Embedded Framework (CEF) is an open source framework for embedding a web browser control based on Google Chrome, it is a convenient way to implement an HTML5 based GUI in a desktop application or to provide browser capabilities to an application. It comes with bindings for C, C++, Delphi, Java, .NET, and Python and runs on Linux, Mac OS X, and Windows.
Other
78 stars 22 forks source link

Needs detailed build Instructions for ARM embedded devices #1

Open teknoman117 opened 9 years ago

teknoman117 commented 9 years ago

So for the last two days I've been attempting to build CEF and run it on an embedded Linux device (like in the video of your software - https://www.youtube.com/watch?v=1asY9y5xQWE). I have a buildroot which is generating an embedded Linux image. The only rendering option I have is EGL + OpenGL ES 2/3. For the most part I followed the instructions I found here - http://www.magpcss.org/ceforum/viewtopic.php?f=10&t=12339&sid=748508f1042fb51195e09d168bf8522c, but I haven't been able to successfully build for arm. I'm trying to merge it with these instructions here - http://unix.stackexchange.com/questions/176794/how-do-i-cross-compile-chromium-for-arm, as manually setting the compilers resulted in failure as it couldn't find the c++ headers.

Also, i've seen some people say you have to change ozone_platform_dri to 0, as some of those files includes the xf86drm headers. How do I build and run your port of CEF without X on EGL? I also noticed you have another repository for an EGL ozone renderer.

Just asking for some detailed instructions, so that it is easier to reproduce what you've done here.

zoltan-ongithub commented 9 years ago

Hi,

there are OE recipes in meta-browser: https://github.com/OSSystems/meta-browser Br,

Zoltan

teknoman117 commented 9 years ago

Since I'm trying to do this without open embedded (using buildroot), I have a couple of questions about the bit bake recipe for cef ( https://github.com/OSSystems/meta-browser/blob/master/recipes-browser/chromium/cef3_280796.bb).

I downloaded the archive from people.linaro.org, which extracts to "chromium_rev_280796." The two git repositories populate the src/ subdirectory according to the functionality of destsuffix. It would seem that the file layout would be like this in work dir.

chromium_rev_280796/ src/ src/cef src/ui/ozone/.....

Not being an open embedded user, all I could glean from the S variable is that is the "source" directory. If this is true, the build script would seem to use the version of cef at chromium_rev_280796/cef instead of the one downloaded from the git (which is only a commit ahead of the one in the archive it seems). I also couldn't find anything on what the "--depth ../" does for create projects. Is the bitbake recipe only using what was in the original archive or is it translating anything prefixed with src/ into ${S}/ ?

I'm just trying to get a grasp on what this is doing so I can write a buildroot script for it.

On Mon, Jul 13, 2015 at 1:58 PM, Zoltan Kuscsik notifications@github.com wrote:

Hi,

there are OE recipes in meta-browser: https://github.com/OSSystems/meta-browser Br,

Zoltan

— Reply to this email directly or view it on GitHub https://github.com/kuscsik/chromiumembedded/issues/1#issuecomment-121057468 .

teknoman117 commented 9 years ago

Or does it unpack like this? In this case, which cef directory does it use?

Chromium_rev_280796/ regular chromium source Chromium_rev_280796/src/ Chromium_rev_280796/src/cef/ Chromium_rev_280796/src/ui/ozone/platform/egl