linux/meta-qt5.git, branch upstream/rocko

qtchooser: drop useless patch, set PV

2020-04-13T11:43:27+00:00

* set PV to something better than just 'git' * drop 0001-Makefile-install-the-man-dir.patch, the change was already applied long before the currently used SRCREV, do_patch WARNING: was correctly complaining: WARNING: qtchooser-git-r0 do_patch: Some of the context lines in patches were ignored. This can lead to incorrectly applied patches. The context lines in the patches can be updated with devtool: devtool modify devtool finish --force-patch-refresh Then the updated patches and the source tree (in devtool's workspace) should be reviewed to make sure the patches apply in the correct place and don't introduce duplicate lines (which can, and does happen when some of the context is ignored). Further information: http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450 Details: Applying patch 0001-Makefile-install-the-man-dir.patch patching file Makefile Hunk #1 succeeded at 2 with fuzz 1 (offset 1 line). Hunk #2 succeeded at 79 with fuzz 2 (offset 22 lines). Now at patch 0001-Makefile-install-the-man-dir.patch Signed-off-by: Martin Jansa

qtbase: fix umask for do_generate_qt_environment_file

2020-04-13T11:40:40+00:00

The custom task "do_generate_qt_environment_file" generates the directory "environment-setup.d" with permission 775 instead of 755. When other recipes populate the same directory with different permissions, a package manager like RPM will report this as an error. The solution is to either set the installation permissions explicitly with "install -d [-m 755]", or specify the umask for the custom task. This commit uses the latter approach and fixes errors like the following when trying to generate an SDK: $ bitbake -c populate_sdk [...] Error: Transaction check error: file /opt/poky/2.4.2/sysroots/x86_64-pokysdk-linux/environment-setup.d conflicts between attempted installs of nativesdk-cmake-3.8.2-r0.x86_64_nativesdk and nativesdk-qtbase-tools-5.9.4+git0+0d9208cecb-r0.x86_64_nativesdk A detailed discussion about this problem can also be found here [1]. [1] https://stackoverflow.com/a/49003464 Signed-off-by: Dennis Menschel Signed-off-by: Martin Jansa

qt5: upgrade to Qt 5.9.9

2020-03-13T07:27:29+00:00

Additionally, update recipes with relevant diff from Qt Company maintained meta-qt5 (5.9) layer. It has few commits & some upstream content merge based changes never upstreamed for one reason or another (license alterations & other minor things). Signed-off-by: Mikko Gronoff

qt5: update SRCREVs after v5.9.8 tags were downmerged to 5.9 branch

2019-05-02T21:24:26+00:00

* there are only a few functional changes: qtdeclarative: 9d6d2ee21 Use Los Angeles to represent PST8PDT, not Vancouver qtimageformats: 11a7040 Update bundled libtiff to version 4.0.10 the rest are just change files Signed-off-by: Martin Jansa

qt5: upgrade to 5.9.8

2019-04-22T06:47:41+00:00

* unfortunatelly most of the modules don't have the v5.9.8 tags merged to 5.9 branch yet, the only exception are: qtnetworkauth, qtremoteobjects, qttranslations * in most cases it means that we're missing just changes files, but in some cases there are also some functional commits which are missing in 5.9 SRCREV: qtdeclarative: 9d6d2ee21 Use Los Angeles to represent PST8PDT, not Vancouver qtimageformats: 11a7040 Update bundled libtiff to version 4.0.10 Signed-off-by: Martin Jansa

qtbase: refresh patches to apply cleanly and update them on github.com/meta-qt5 forks

2019-04-19T12:26:39+00:00

* in preparation for 5.9.8 upgrade Signed-off-by: Martin Jansa

qtscript: update LIC_FILES_CHKSUM entries

2018-11-02T16:37:23+00:00

Upstream commit 51303a9ee793cdf952e165e30c50310a5ec753d6 updated license files: http://code.qt.io/cgit/qt/qtscript.git/commit/?h=5.9&id=51303a9ee793cdf952e165e30c50310a5ec753d6 Signed-off-by: Denys Dmytriyenko Signed-off-by: Martin Jansa

qt5: upgrade to 5.9.7

2018-11-01T13:31:22+00:00

* Update to Qt 5.9.7 * qtbase: default to internal harfbuzz-ng: With -no-harfbuzz, Qt uses internal copy of harfbuzz-old, which is no longer maintained, and is extremely buggy. Instead, use the harfbuzz-ng version if system harfbuzz is not used. Signed-off-by: mikko.gronoff Signed-off-by: Martin Jansa

qtbase: don't use thumb for armv[45]

2018-10-15T15:21:48+00:00

* it fails when building with gcc8 Signed-off-by: Martin Jansa

qt: upgrade to 5.9.6

2018-06-16T09:45:29+00:00

Signed-off-by: Martin Jansa