| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
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>
|
|
Bump revision to include:
* 3169198 [BACKPORT] skia: Build skcms with -mfp16-format=ieee on GCC ARM builds
* 6aa7e63 [BACKPORT] libavcodec: Remove dynamic relocs from h264idct_neon.S
These patches were being kept in the recipe, but there is no need for
that now.
Bug-AGL: SPEC-2506
Bug-AGL: SPEC-2514
Change-Id: I7dcd221c7f4fc179f2e686c8cc4eb619917ad9ab
Signed-off-by: Jacobo Aragunde Pérez <jaragunde@igalia.com>
|
|
Backport upstream patch:
https://chromium-review.googlesource.com/c/chromium/third_party/ffmpeg/+/1390286
Fix this error when linking libcbe.so:
obj/third_party/ffmpeg/ffmpeg_internal/
autorename_libavcodec_aarch64_h264idct_neon.o:
relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol
`ff_h264_idct8_add_neon' which may bind externally can not be used
when making a shared object; recompile with -fPIC
Also remove the mksnapshot path override for aarch64, it is not
necessary now we run mksnapshot with qemu. This fixes the install
step.
Bug-AGL: SPEC-2506
Change-Id: Idb90c8c20910ec48ed01f1b02528f14781edc4a3
Signed-off-by: Nick Yamane <nickdiego@igalia.com>
Signed-off-by: Jacobo Aragunde Pérez <jaragunde@igalia.com>
|
|
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>
|
Jacobo Aragunde Pérez