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

qt5webkit: select leveldb package and memenv

2019-03-25T10:41:10+00:00

This patch fixes the build issue reported by autobuilder [0]. /home/naourr/work/instance-2/output/build/qt5webkit-5.9.1/Source/WebCore//.obj/platform/leveldb/LevelDBDatabase.o: In function `WebCore::LevelDBDatabase::openInMemory(WebCore::LevelDBComparator const*)': LevelDBDatabase.cpp.text._ZN7WebCore15LevelDBDatabase12openInMemoryEPKNS_17LevelDBComparatorE+0x34): undefined reference to `leveldb::NewMemEnv(leveldb::Env*)' collect2: error: ld returned 1 exit status make[3]: *** [Makefile.api:97: ../lib/libQt5WebKit.so.5.9.1] Error 1 The issue happens when both packages leveldb and qt5webkit are enabled. QtWebKit builds its own copy of leveldb [1] (as a third-party) if the system does not provided it (i.e. buildroot). It builds it differently and this is the origin of that issue. Instead of using the Makefile provided by leveldb [2], QtWebKit uses qmake to build that library [3]. The missing symbol issue happens because the symbol leveldb::NewMemEnv is bundled in the static library libmemenv.a (aside libleveldb.so). This static library consists of this single symbol which is like an extra that is built but *NOT* shipped by default at installation in the staging directory. Unfortunatly, that symbol is required later by WebCore [4]. The copy built by QtWebKit is an all-in-one library including both libleveldb and libmemenv; thus QtWebKit links against libleveldb only. Also, the linker finds the buildroot's copy first (not the third-party): that explains why it is complaining about a missing symbol. That copy does not have the symbol leveldb::NewMemEnv. Fortunatly, QtWebKit provides a facility to link against the system leveldb package. The qmake flag WEBKIT_CONFIG+=use_system_leveldb tells Qt5WebKit to link against libleveldb *AND* libmemenv [5]. To fix that issue, this commit selects the package leveldb that now installs the libmemenv static library and its header. It ensures that QtWebKit has everything it needs to be built. It also sets the appropriate qmake configure flags to tell QtWebKit to use the leveldb copy built by buildroot instead of the bundled one. [0]: http://autobuild.buildroot.net/results/46033e82adf592c3b92c6d50cfaf45bd58beeaa4 [1]: https://github.com/qt/qtwebkit/tree/5.9/Source/ThirdParty/leveldb [2]: https://github.com/qt/qtwebkit/blob/5.9/Source/ThirdParty/leveldb/Makefile#L167-L169 [3]: https://github.com/qt/qtwebkit/blob/5.9/Source/ThirdParty/leveldb/Target.pri#L80 [4]: https://github.com/qt/qtwebkit/blob/5.9/Source/WebCore/platform/leveldb/LevelDBDatabase.cpp#L185 [5]: https://github.com/qt/qtwebkit/blob/5.9/Source/WebCore/WebCore.pri#L254 [6]: https://github.com/google/leveldb/commit/739c25100e46576cdcdfff2d6f43f9f7008103c7 Signed-off-by: Gaël PORTAY Signed-off-by: Arnout Vandecappelle (Essensium/Mind) (cherry picked from commit 2d7c746ed8c89ad262ef0c6db5460ade1fc35973) Signed-off-by: Peter Korsgaard

package/qt5/qt5base: add BR2_PACKAGE_QT5BASE_OPENSSL

2019-03-04T20:13:21+00:00

Commit c110e48cecde6f543da18388322907b05b25e7d2 disabled openssl support on QT 5.6, this has the side-effect of breaking the build of python-pyqt5 because support of openssl is enabled on python-pyqt5 if BR2_PACKAGE_OPENSSL is selected To fix this issue, add a new BR2_PACKAGE_QT5BASE_OPENSSL option in qt5base and use it in python-pyqt5 Fixes: - http://autobuild.buildroot.org/results/e92991308d47649cecc4084e41ab5711ec96831f Signed-off-by: Fabrice Fontaine [Peter: make _OPENSSL a blind option, add libressl logic for 5.6.x] Signed-off-by: Peter Korsgaard

package/qt5/qt5base: build Qt 5.6 with LibreSSL if present

2019-03-04T19:22:57+00:00

LibreSSL build is successful with shared linkage, but not default dlopen(). Also adds patch for successful compilation by using -fpermissive. Signed-off-by: James Grant Signed-off-by: Peter Korsgaard

package/qt5/qt5base: exclude OpenSSL functionality for Qt 5.6.x

2019-03-01T09:13:14+00:00

No patch back-porting OpenSSL 1.1.x support to Qt 5.6.x is available. https://development.qt-project.narkive.com/RW4wxYXY/openssl-1-1-x-support-on-qt-5-6-5-9 Signed-off-by: James Grant Signed-off-by: Peter Korsgaard

package/qt5/qt5base: add custom configure options last

2019-03-01T09:12:36+00:00

This allows all options set by Buildroot to be overridden. Signed-off-by: James Grant [Peter: drop original line as pointed out by Thomas] Signed-off-by: Peter Korsgaard

package/qt5base: fix double-conversion compile for riscv

2019-02-24T20:30:20+00:00

Fixes [1], [2]: ../3rdparty/double-conversion/include/double-conversion/utils.h:83:2: error: #error Target architecture was not detected as supported by Double-Conversion. [1] http://autobuild.buildroot.net/results/8bdb6a2b56f6ea96649184e5fef6ce2c56b9ec2b [2] http://autobuild.buildroot.net/results/63ba267674b424786bb10c97c565f4306147f95a Signed-off-by: Peter Seiderer Signed-off-by: Thomas Petazzoni

package/qt5/qt5base: handle sse2/sse3/ssse3/sse4.1/sse4.2/avx/avx2 configuration

2019-02-15T21:49:21+00:00

The Qt configure auto detection (and announced runtime detection feature) failes (see e.g. [1]), so override the configuration with the buildroot determined settings. [1] http://lists.busybox.net/pipermail/buildroot/2019-January/241862.html Reported-by: David Picard Signed-off-by: Peter Seiderer Signed-off-by: Thomas Petazzoni

package/qt: remove package

2019-02-06T14:47:13+00:00

Qt4 has been marked obsolete for close to 1 year, since commit 3538b5fb10 (qt: mark as obsolete) and is no longer supported upstream since December 2015: https://blog.qt.io/blog/2015/05/26/qt-4-8-7-released/ So now finally remove it as the in tree users have been removed. Signed-off-by: Peter Korsgaard Signed-off-by: Arnout Vandecappelle (Essensium/Mind)

package/qt5/qt5base: do not change QMAKE_COMPILER in g++-base.conf

2018-12-10T19:49:09+00:00

The variable QMAKE_COMPILER determines the compiler flavour (e.g. gcc, clang, llvm, msvc etc.) and not a compiler path. Changing it confuses the platform test of the qt5webengine package (mkspecs/features/platform.prf): defineTest(isPlatformSupported) { QT_FOR_CONFIG += gui-private linux { if(!gcc:!clang)|intel_icc { skipBuild("Qt WebEngine on Linux requires clang or GCC.") return(false) } gcc:!clang:!isGCCVersionSupported(): return(false) } } Revert the variable change introduced by commit 'package/qt5/qt5base: use ccache for building host code' ([2]). Fixes raspberrypi3_qt5we_defconfig/qt5webengine build ([1]): Qt WebEngine on Linux requires clang or GCC. QtWebEngine will not be built. [1] https://gitlab.com/buildroot.org/buildroot/-/jobs/131217091 [2] https://git.buildroot.net/buildroot/commit/?id=c2ea056a1b34fd1354100d08e603b9374e225968 Signed-off-by: Peter Seiderer Signed-off-by: Thomas Petazzoni

package/qt5/qt5virtualkeyboard: rewrap Config.in help text

2018-12-09T21:50:12+00:00

check-package complains with: package/qt5/qt5virtualkeyboard/Config.in:59: help text: <2 spaces><62 chars> (http://nightly.buildroot.org/#writing-rules-config-in) So let's rewrap the Config.in help text. Signed-off-by: Thomas Petazzoni