chromium68: custom toolchain, target v8 snapshot 85/21685/4
authorJacobo Aragunde Pérez <jaragunde@igalia.com>
Mon, 17 Jun 2019 11:12:00 +0000 (13:12 +0200)
committerJan-Simon Moeller <jsmoeller@linuxfoundation.org>
Thu, 20 Jun 2019 12:57:47 +0000 (12:57 +0000)
commite6cc8d4e0977b4a3dda28c70caea3515f9d07edd
tree37493398c6f35728ca73cc36c64e91e9bed33c1a
parent13e42025cf8c2b6f5b8d10666353e60da7d52370
chromium68: custom toolchain, target v8 snapshot

Modify the chromium68 recipe to make it more like the one available in
meta-browser: https://github.com/OSSystems/meta-browser

Instead of passing Yocto's build flags to the cros (=ChromeOS)
toolchain, generate a toolchain definition file specifically for this
build.

For the generation of the V8 memory snapshot, build the required files
for the target architecture, then use qemu-native to run them.
Upstream chromium addresses this problem by downloading a specific
native toolchain for every target platform, which we cannot do in this
context.

The toolchain changes trigger an issue with ARMv7 builds; backported
one patch to address that specific issue.

This changes also triggered a problem with 32 bit targets, the
generated binaries were too big. Forced the DEBUG_ARGS to use -g1 (or
-g0 otherwise).

Bug-AGL: SPEC-2514

Change-Id: Ib18431b628415c58a3c29595bfff10057e355a4b
Signed-off-by: Jacobo Aragunde Pérez <jaragunde@igalia.com>
meta-html5-framework/recipes-wam/chromium/chromium68/0001-skia-Build-skcms-with-mfp16-format-ieee-on-GCC-ARM-b.patch [new file with mode: 0644]
meta-html5-framework/recipes-wam/chromium/chromium68/v8-qemu-wrapper.patch [new file with mode: 0644]
meta-html5-framework/recipes-wam/chromium/chromium68_git.bb
meta-html5-framework/recipes-wam/chromium/gn-utils.inc