buildroot/package/qt5/qt5webengine, branch 2019.02-op-build

qt5: bump latest version to 5.11.3

2018-12-08T19:57:37+00:00

qt5base: remove 0005-Export-qt_open64-from-QtCore.patch (taken from upstream [1]) [1] http://code.qt.io/cgit/qt/qtbase.git/commit/?id=4fc4f7b0ce0e6ee186a7d7fe9b5dd20e94efe432 Signed-off-by: Peter Seiderer Signed-off-by: Peter Korsgaard

qt5: bump latest version to 5.11.2

2018-09-30T18:00:00+00:00

- qt5canvas3d: update license info - qt5serialbus: update license hash (LICENSE.FDL editorial change, see [1]) - qt5serialport: update license hash (LICENSE.FDL editorial change, see [2]) [1] https://code.qt.io/cgit/qt/qtserialbus.git/commit/?id=226bd2f84c807b5401a82832dafa48d34966052a [2] https://code.qt.io/cgit/qt/qtserialport.git/commit/?id=e0bd3949c30ce9c1988a6d6a3c0850d16a1fb33a Signed-off-by: Peter Seiderer Signed-off-by: Peter Korsgaard

qt5webengine: use QT5WEBENGINE prefix for CHROMIUM_LICENSE_FILES variable

2018-09-01T12:45:22+00:00

The qt5webengine package currently uses the CHROMIUM_LICENSE_FILES variable to hold the list of license files for the chromium source code embedded inside the qt5webengine code. However, using this variable would clash with a hypothetical "chromium" package, and anyway violates our rule that all variables of a package should be prefixed by the package name. This commit fixes that by adding the QT5WEBENGINE to this variable. Signed-off-by: Laurent Hartanerot Signed-off-by: Thomas Petazzoni

qt5webengine: fix chromium-latest.inc with the current license files

2018-09-01T12:45:22+00:00

chromium-latest.inc was not properly updated with the latest version bumps of Qt, and it no longer matches the license files of Qt5Webengine 5.11. This commit fixes this legal-info failure: $ make qt5webengine-legal-info [...] cp: cannot stat '/home/thomas/projets/buildroot/output/build/qt5webengine-5.11.1/src/3rdparty/chromium/buildtools/third_party/libc++abi/trunk/LICENSE.TXT': No such file or directory Signed-off-by: Laurent Hartanerot Signed-off-by: Thomas Petazzoni

qt5webengine: rename chromium.inc to chromium-latest.inc

2018-09-01T12:45:22+00:00

For consistency with chromium-lts.inc, rename chromium.inc to chromium-latest.inc. Signed-off-by: Laurent Hartanerot Signed-off-by: Thomas Petazzoni

qt5webengine: add separate file for chromium license files for Qt LTS

2018-09-01T12:45:22+00:00

The qtwebengine package used by Qt LTS has a different set of license files for chromium, so this commit introduces a separate chromium-lts.inc with the right contents. This fixes legal-info of qt5webengine with Qt LTS. Signed-off-by: Laurent Hartanerot Signed-off-by: Thomas Petazzoni

qt5: bump latest version to 5.11.1

2018-07-01T09:06:08+00:00

qtwebengine: Remove 0001-Fix-build-with-GCC-8.1.0.patch (upstream since [1]). [1]: https://github.com/qt/qtwebengine/commit/08db7562bf7709122807f151cab710b3fd9d7c19 Signed-off-by: Gaël PORTAY Reviewed-by: Peter Seiderer Signed-off-by: Thomas Petazzoni

qt5webengine: propagate parallel flag to ninja

2018-07-01T09:04:59+00:00

WebEngine is a big project to build. It uses ninja which is a build system that does everything in parallel[1]. Builds are always run in parallel, based by default on the number of CPUs your system has. Underspecified build dependencies will result in incorrect builds. QtWebEngine does not propagate the parallel flag from the running instance of make to ninja. Thus, all the machine cores are used to build this single project. make -j 10 -> ninja -j # all cores This behavior disrupts powerful machines which are setup to build many projects in parallel. Even worse, the build fails on machines where the ratio CPU-cores / amount of RAM (including swap) is not appropriate. g++ may have not enough of memory to build all those files in parallel. Unfortunatly, the target `run_ninja' is hardcoded in the Makefile src/core/Makefile.run_gn; there is no way to propagate flags using a variable through the make command-line. run_ninja: /home/gportay/src/buildroot/output-qt5.11/build/qt5webengine-5.11.1/src/3rdparty/ninja/ninja -C /home/gportay/src/buildroot/output-qt5.11/build/qt5webengine-5.11.1/src/core/release QtWebEngineCore Luckily, the Qt gn_run.pro[2] can hardcode ninja extra flags through the variable NINJAFLAGS when the Makefile is generated (which is performed during the build and not during configure step). This commit sets the NINJAFLAGS using the variable PARALLEL_JOBS to limit the number of cores used by ninja. Fixes: virtual memory exhausted: Cannot allocate memory [1]: https://ninja-build.org/manual.html#_comparison_to_make [2]: https://github.com/qt/qtwebengine/blob/v5.11.1/src/core/gn_run.pro#L49-L53 CC: Damien Riegel CC: Jean-François Têtu Signed-off-by: Gaël PORTAY Acked-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

qt5: bump latest version to 5.11.0

2018-06-17T21:28:27+00:00

qtwayland: Remove 0001-Fix-compilation-for-Renesas-R-Car-M3.patch (upstream since [1]). qtwebengine: New 3rd-part 0001-Fix-build-with-GCC-8.1.0.patch (upstream in chromium [2]). [1]: https://github.com/qt/qtwayland/commit/8b204b2c56be5e7c1fd21144ae140c9b865dd86b [2]: https://codereview.qt-project.org/#/c/229160/ Signed-off-by: Gaël PORTAY Signed-off-by: Thomas Petazzoni

qt5webengine: fix BR2_TOOLCHAIN_HAS_GCC_BUG_85862 condition

2018-06-13T20:55:31+00:00

In commit bd03966d4ebeb284ac3afb5f3b8cba13da2b9983 ("toolchain: GCC bug 85862"), a dependency on BR2_TOOLCHAIN_HAS_GCC_BUG_85862 was added to the qt5webengine package, but it should have been a dependency on !BR2_TOOLCHAIN_HAS_GCC_BUG_85862. This commit fixes that. Signed-off-by: David Barbion Reviewed-by: Matt Weber Signed-off-by: Thomas Petazzoni