[yocto] Compiling meta-browser ==>chromium ? cleaning ?
gandersson at genivi.org
Sun Jun 18 11:10:34 PDT 2017
Riko Ho <antonius.riko at gmail.com> wrote:
> Hello Everyone,
> I tried to compile chromium but never succeeded, took me already 12
> hours and stopped on 99%, I used bitbake for doing it,
Not sure what would cause it to just stop and it could have been some
temporary glitch? Maybe you want to provide some logs of your build if
Martin's reference does not help.
> Is chromium not compatible with arm CPU ? it was working with X86_64
Is it a Wayland based project or X based desktop type?
GENIVI worked with Igalia to update chromium support for Wayland. You can
take a look at the feature branch for GENIVI Development Platform  if it
helps. I think you'd need to work out why your build freezes completely
Since it's a work in progress I don't guarantee that it is clean or easy to
follow yet. A lot of workarounds and tweaks: . We're temporarily on a
fork of ozone-wayland because of recent multi-screen support for example.
It builds and runs on Renesas R-Car generation 3 (64 bit ARMv8). It builds
on Raspberry Pi as well but there's a runtime problem. And of course x86_64
like e.g. Minnowboard. It seems to need a few unique tweaks for every ARM
board so I guess it depends what you are doing.
Please feel free to help us get things extracted out of there and into meta-
browser and chromium or ozone upstream. We're focusing first on fixing the
boards that don't work and then we'll know more what the final patches for
upstream should look like.
> And how can I clean after building it ? It took about 70Gb of my drive
You could also try INHERIT += "rm_work"
see , item 4.
Hope this helps
Gunnar Andersson <gandersson at genivi.org>
More information about the yocto