summaryrefslogtreecommitdiffstats
path: root/meta-html5-framework/recipes-wam/chromium/chromium68/v8-qemu-wrapper.patch
AgeCommit message (Collapse)AuthorFilesLines
2019-12-06meta-html5-framework: rename layer and featureicefish_8.99.2icefish/8.99.28.99.2Jacobo Aragunde Pérez1-40/+0
The new name for the layer is meta-agl-profile-graphical-html5 and the feature is agl-profile-graphical-html5, which better match the other existing features like agl-profile-graphical-qt5. Usage: aglsetup.sh -m $MACHINE agl-profile-graphical-html5 Build minimal image to run HTML5 apps: bitbake agl-image-graphical-html5 Include to agl-demo-platform: IMAGE_INSTALL_append = " packagegroup-agl-appfw-html5" Change-Id: I4a4d4f85dd7fc23be51621702f842aa86a0dc3a5 Signed-off-by: Jacobo Aragunde Pérez <jaragunde@igalia.com>
2019-06-20chromium68: custom toolchain, target v8 snapshotJacobo Aragunde Pérez1-0/+40
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>