From: Gunnar Andersson <gandersson@genivi.org>
To: yocto@yoctoproject.org
Subject: Re: Compiling meta-browser ==>chromium ? cleaning ?
Date: Sun, 18 Jun 2017 20:10:34 +0200 [thread overview]
Message-ID: <1497809434.2788.77.camel@genivi.org> (raw)
In-Reply-To: <mailman.66247.1497786545.15860.yocto@yoctoproject.org>
Riko Ho <antonius.riko@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
> before.
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 [1] if it
helps. I think you'd need to work out why your build freezes completely
first, however.
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: [2]. 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 [3], item 4.
Hope this helps
- Gunnar
[1] https://github.com/genivi/genivi-dev-platform/tree/chromium/
[2] https://github.com/GENIVI/genivi-dev-platform/blob/chromium/meta-genivi-dev/meta-genivi-dev/recipes-extended/chromium/chromium-wayland_%25.bbappend
[3] http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#building-an-image-for-emulation
--
Gunnar Andersson <gandersson@genivi.org>
Development Lead
GENIVI Alliance
>
> Thanks
next parent reply other threads:[~2017-06-18 18:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.66247.1497786545.15860.yocto@yoctoproject.org>
2017-06-18 18:10 ` Gunnar Andersson [this message]
2017-06-19 14:21 ` Compiling meta-browser ==>chromium ? cleaning ? Jacobo Aragunde Pérez
2017-06-19 20:01 ` Khem Raj
2017-06-20 3:32 ` Riko Ho
2017-06-20 5:08 ` Khem Raj
2017-06-21 1:53 ` Riko Ho
2017-06-21 2:28 ` Khem Raj
2017-06-21 4:38 ` Riko Ho
2017-06-21 4:42 ` Riko Ho
2017-06-21 7:37 ` Gunnar Andersson
2017-06-21 8:18 ` Riko Ho
2017-06-21 8:24 ` Riko Ho
2017-06-23 3:40 ` 47401300.usb-phy supply vcc not found, using dummy regulator Riko Ho
2017-06-24 4:52 ` Compiling meta-browser ==>chromium ? cleaning ? Riko Ho
2017-06-14 4:10 bitbake core-image-web-kiosk question ? Riko Ho
2017-06-14 5:38 ` Khem Raj
2017-06-15 5:53 ` FriendlyArm Mini6410 ? Riko Ho
2017-06-15 6:05 ` Belisko Marek
2017-06-17 23:41 ` Compiling meta-browser ==>chromium ? cleaning ? Riko Ho
2017-06-18 7:49 ` Martin Jansa
2017-06-18 7:52 ` Riko Ho
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=1497809434.2788.77.camel@genivi.org \
--to=gandersson@genivi.org \
--cc=yocto@yoctoproject.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.