summaryrefslogtreecommitdiffstats
path: root/meta-html5-framework/recipes-wam
AgeCommit message (Collapse)AuthorFilesLines
2019-10-11wam: bump revisionAntia Puentes1-1/+1
Includes commits: * [agl] Implement an envvar for launcher to wait for host process * [agl] Suspend/resume webapps depending on visibility * Create socket and lock files in XDG_RUNTIME_DIR. which are the fixes for the AGL issues: Bug-AGL: SPEC-2793 Bug-AGL: SPEC-1948 Bug-AGL: SPEC-2684 Change-Id: I1dc64ca013804c5df9a7f17f6d6722d40f3271f1 Signed-off-by: Antia Puentes <apuentes@igalia.com>
2019-10-08chromium68: bump revision, it fixes a WAM crash in rpiAntia Puentes1-1/+1
Includes commit: * Revert "[BACKPORT] [ozone/wayland] Use gbm with in-process-gpu mode" The original Chromium backport introduced a regression in the Raspberry Pi, resulting in a crash in the WebAppMgr. Bug-AGL: SPEC-2790 Change-Id: Ibc7af04cbd0b867d1488bcb18926d3337ad998ef Signed-off-by: Antia Puentes <apuentes@igalia.com>
2019-09-25wam: auto-enable remote debug when agl-devel is onAntia Puentes1-0/+7
Apart from preventing remote debugging when agl-devel is not set, which was tackled in SPEC-2327, we are interested in having remote debugging available by default when agl-devel is set. WAM checks if files: * /var/agl-devel/preferences/devmode_enabled * /var/agl-devel/preferences/debug_system_apps exist to enable the dev mode and the remote web inspector, so we create those files by default when agl-devel is set. Bug-AGL: SPEC-2782 Change-Id: I557a633802e6baa15339708b00719d66adbcf1ac Signed-off-by: Antia Puentes <apuentes@igalia.com>
2019-08-27chromium68: remove downstream backportsJacobo Aragunde Pérez3-175/+1
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>
2019-08-26chromium68: bump revisionAntia Puentes1-1/+1
Commits included are backports from Chromium/Wayland upstream which are part of the on-going work carried on SPEC-2266: 6a0470f2d03 [BACKPORT] [ozone/wayland] rely on implicit sync for Broadcom and Intel GPUs. 55acfb83ea4 [BACKPORT] [ozone/wayland] Use gbm with in-process-gpu mode d58f1321884 [BACKPORT] ozone: xkbcommon: Pre-compute masks when setting keymap ce84756108d [BACKPORT] ozone/wayland: xkbcommon: Fix layout switching 5e8508b280e [BACKPORT] ozone/wayland: Support NumLock in non-chromeos builds 7e90082ccfc [BACKPORT] ozone/wayland: Remove WaylandXkbKeyboardLayoutEngine c74c5365d40 [BACKPORT] ozone/wayland: Fix NEO keyboards layout handling 1055757769d [BACKPORT] ozone/wayland: Support dead keys e2648e9c17b [BACKPORT] Move CharacterComposer into //ui/base/ime Besides: * 1055757769d [BACKPORT] ozone/wayland: Support dead keys fixes SPEC-2746 * 55acfb83ea4 [BACKPORT] [ozone/wayland] Use gbm with in-process-gpu mode fixes SPEC-2699 Bug-AGL: SPEC-2266 Bug-AGL: SPEC-2746 Bug-AGL: SPEC-2699 Change-Id: I19eaa6bf225ac478386c53b94955ccb0a4856e62 Signed-off-by: Antia Puentes <apuentes@igalia.com> (cherry picked from commit d656495e536f0fefcbfde84599afd79b40aa3c88)
2019-07-25meta-html5-framework/wam: adjust how wam is startedStephane Desneux3-14/+249
WebAppMgr has to be launched for each user (but not through the systemd user session as it would require too much privileges for the user). For this purpose, we create a systemd service instanciated for each user by the application framework through afm-user-session@ service. This patch also distributes the environment and service file near the recipe instead of having those integration files in the sources (it's easier to follow AGL evolution without changing the upstream source code) Also, for the HTML5 demos to work, each app must request the following permissions in their config.xml: <param name="urn:AGL:permission::public:display" value="required" /> <param name="urn:AGL:permission::public:audio" value="required" /> Bug-AGL: SPEC-2586 Change-Id: I4286fd9e1d1a1dcff48d3fdbfab2bf8d57f0fa0e Signed-off-by: Stephane Desneux <stephane.desneux@iot.bzh>
2019-07-13wam: bump revision, fixes related to the remote inspectorhalibut_7.99.3halibut/7.99.37.99.3Antia Puentes1-1/+1
Included changes: * 8271e13 [agl] Update the path for the Remote Web Inspector * f0166b5 [agl] Remote debugging should work only on debug mode AGL-bug: SPEC-2327 AGL-bug: SPEC-2328 Change-Id: Iaee96758831d0d1e809bd10e0ce6dff445d6210a Signed-off-by: Antia Puentes <apuentes@igalia.com>
2019-07-13wam: add AGL_DEVEL flag if 'agl-devel' distro feature is onAntia Puentes1-0/+1
We want the remote inspector to be available only in debug mode, i.e. when the 'agl-devel' feature is on. We will use this flag to check if that is the case. AGL-bug: SPEC-2327 Change-Id: Ib22c5f21bc79afa4544b884238ca971d7bef6991 Signed-off-by: Antia Puentes <apuentes@igalia.com>
2019-07-11chromium: fix launcher for halibutJacobo Aragunde Pérez1-2/+2
Bumps revision and points to newly created halibut branch. Included changes: * 7dabb46 Do not set the user-data-dir. * f0821a3 Add the new display permission to config.xml.in. AGL-Bug: SPEC-2612 Change-Id: Ie0bdc7dfc840523e262f34b53c2a6945743345dd Signed-off-by: Jacobo Aragunde Pérez <jaragunde@igalia.com>
2019-07-04chromium68: do not set mksnapshot path env varsAntia Puentes1-3/+0
Bug-AGL: SPEC-2602 Change-Id: I7b8756d8be3384ccaff18ecbaf11bb163e2a3c3e Signed-off-by: Antia Puentes <apuentes@igalia.com>
2019-06-29chromium68: fix aarch64 link issuehalibut_7.99.2halibut/7.99.27.99.2Jacobo Aragunde Pérez2-1/+110
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>
2019-06-27wam: revision bump, fix linker issuesJacobo Aragunde Pérez1-1/+1
Included changes: * 574c65b [agl] Explictly link WAM binary with WAMCore lib * 9244327 [agl] Explicitly link WAM binary with ilmCommon library Bug-AGL: SPEC-2532 Change-Id: I8ea9ed51d404b902d954f3e90a05daced7119361 Signed-off-by: Jacobo Aragunde Pérez <jaragunde@igalia.com>
2019-06-27wam: Remove any Qt dependencies and port to CMakeJacobo Aragunde Pérez2-10/+10
Recipe changed to use CMake instead of QMake. After Qt usage removal from WAM implementation, boost is now used for some functionalities previously provided by Qt (e.g: File system). Additionally, add glib-2.0 missing dependency. Finally, bump to latest WAM. Included changes: 3e9ce0d [agl][qtless] Port to CMake 971df2a [agl][qtless] Use unordered_map instead of std::map aaa56e3 [agl][qtless] Get rid of Qt usage in webos/DeviceInfoImpl 20a1ec2 [agl][qtless] Remove Qt dependency from qmake files 2615c15 [agl][qtless] Use const char arrays instead of macros for WindowTypes 42770ee [agl][qtless] Trim timestamp string in NetworkStatus 0c7d257 [agl][qtless] Replace QLocale by Boost.Locale 45108f9 [agl][qtless] Remove QVariant leftovers 00f7a1f [agl][qtless] Add Url parsing code 9f74ec6 [agl][qtless] QString-less WAM: Remove leftovers a5ebdc5 [agl][qtless] Migrate PalmSystem away from QString 41ecf4c [agl][qtless] Do not use QString in WebAppManagerConfig 815191c [agl][qtless] Do not use QString in NetworkStatus 47bd88b [agl][qtless] Do not use QString in WebPage ba7ece0 [agl][qtless] Migrate WebAppWayland away from QVariant 903e2fa [agl][qtless] QString-less WebApp: Remove leftovers 502b9f6 [agl][qtless] QString-less WebApp/WebPage: appId 20f57de [agl][qtless] QString-less WebAppManager: SystemLanguage and DeviceInfo e055f56 [agl][qtless] Do not use QString WebAppManager in JS strings building 8949895 [agl][qtless] Migrate WebAppManager away from QString 75aaf56 [agl][qtless] Get rid of QString usage in WebProcessManager 700e456 [agl][qtless] Migrate ApplicationDescription away from QString ba798eb [agl][qtless] Replace Qt data container types by their STL counterpars 159cef4 [agl][qtless] Fix error handling when converting strings to numbers 9c875f1 [agl][qtless] Add StringUtils initial implementation Bug-AGL: SPEC-1871 Change-Id: I7e7725e6a5e9790fd4660f104e4142084f100b62 Signed-off-by: Nick Diego Yamane <nickdiego@igalia.com> Signed-off-by: Jacobo Aragunde Pérez <jaragunde@igalia.com> (cherry picked from commit fcfbd7497c73413bd35d1a641686f2c095626daa)
2019-06-20chromium68: custom toolchain, target v8 snapshotJacobo Aragunde Pérez4-74/+298
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>
2019-05-02chromium68, wam: bump revisionAntia Puentes2-5/+5
Bug-AGL: SPEC-2353 Change-Id: I2a62e76422a35b5a9c95fa310677199b8ca79146 Signed-off-by: Antia Puentes <apuentes@igalia.com> (cherry picked from commit 0bfe1a36c4bcc9c4d309f9005b2d8da23ca0eed8)
2019-04-29chromium68: Add explicitly bison-native dependencyLorenzo Tilve1-1/+1
After the update from Guppy it seems that Chromium build recipe don't have the bison dependency satisfied, so it is explicitly included now. Change-Id: I184c506b4820e7c3434708594c6d81cd47ce5681 Bug-AGL: SPEC-2342 Signed-off-by: Lorenzo Tilve <ltilve@igalia.com>
2019-01-15Integrate Chromium and WAM recipes.Jacobo Aragunde Pérez5-0/+530
Create a new layer called meta-html5-framework. It contains the following recipes: * chromium68 to build the browser shared library and browser code. * chromium-browser-service for the browser widget. * wam for the web application manager. * wam-tinyproxy is a direct dependency of wam. Defines a new packagegroup, which is added to the agl-demo-platform image in case agl-html5-framework is configured as a feature. Bug-AGL: SPEC-1885 Change-Id: I39f01ab09e198cd139e95ff3c784af563b54329b Signed-off-by: Jacobo Aragunde Pérez <jaragunde@igalia.com> (cherry picked from commit 19e71462fc44093c6f9046e60c72adeedfca7858)