* reading [1] again caused hope bug is fixed
* tested with buildhistory: no change at installed files detected
* recipies affected (lirios/meta-qt5-extra) are building fine (with the patch
following)
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Right now cmake config file installed by qtdeclarative-native tries
to use system installed qmlcachegen tool. Due to this packages using qml
compiler will produce correct results only if the host system has
qmlcachegen installed and its version matches Qt version provided by OE.
If the tool is missing the package requring it will fail to build. If
its present but the version does not match OE version of Qt the package
will build fine, but in turn will fail to run on the target. Fix this by
patching Qt5QuickCompilerConfig.cmake to look for qmlcachegen in
OE_QMAKE_PATH_EXTERNAL_HOST_BINS. Similar approach is already used for
other Qt tools from qtbase-native recipe.
Signed-off-by: Piotr Tworek <tworaz@tworaz.net>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Right now qtbase-native will try to look for double-coversion library on
the host system. If not avaiable it'll use its own copy. This means
qtbase-native binaries built on one host may fail to run on another.
Fix this by always using qt provided double-conversion library for
native qtbase builds.
Signed-off-by: Piotr Tworek <tworaz@tworaz.net>
Fix compiler errors when using clang compiler along the way
Fixes
aarch64-yoe-linux-musl-ld: cannot find -lclang
Use chpath to delete rpath which is detected as path to native clang in
sysroot
Signed-off-by: Khem Raj <raj.khem@gmail.com>
* 4 musl patches didn't apply at all
* 0015-chromium-musl-include-asm-generic-ioctl.h-for-TCGETS.patch is
dropped, because whole chromium/device/serial/serial_io_handler_posix.cc
was removed in upgrade to 73:
commit 38a9a29f4f9436cace7f0e7abf9c586057df8a4e
Author: Allan Sandfeld Jensen <allan.jensen@qt.io>
Date: Wed Feb 13 16:23:34 2019 +0100
Subject: BASELINE: Update Chromium to 73.0.3683.37
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Update recipes for Qt 5.13.0, add new recipes for Qt modules qtcoap
and qtlottie, and remove qtcanvas3d.
Signed-off-by: Samuli Piippo <samuli.piippo@qt.io>
Some Qt build tools may depend on QtGui, which need platform plugins
for running them. Use minimal platform plugin since no interaction
with the tool is expected.
Add PACKAGECONFIGs that can be used to enable gui and image format
plugins for the native and nativesdk builds.
Signed-off-by: Samuli Piippo <samuli.piippo@qt.io>
* some components which use Werror started to fail with gcc-9, because of new warning:
https://gcc.gnu.org/gcc-9/changes.html
New warnings:
-Wdeprecated-copy, implied by -Wextra, warns about the C++11
deprecation of implicitly declared copy constructor and
assignment operator if one of them is user-provided.
-Wdeprecated-copy-dtor also warns if the destructor is
user-provided, as specified in C++11.
* e.g. maliit-framework-qt5 was now failing with:
maliit-framework-qt5/0.99.0+gitAUTOINC+62bd54bcde-r0/recipe-sysroot/usr/include/QtCore/qvariant.h:273:25:
error: implicitly-declared 'constexpr QVariant::Private& QVariant::Private::operator=(const QVariant::Private&)' is deprecated [-Werror=deprecated-copy]
273 | { other.d = Private(); }
| ^
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
A wildcard not put between quotes is expanded by bash. If files matching
the pattern are found in the source directory then the find command is
non-sense and fails.
This commit put those search patterns in quotes and fixes the
installation of some recipes.
Signed-off-by: Florent Revest <revestflo@gmail.com>
* otherwise building qtbase with default config will fail with:
ERROR: The OpenGL functionality tests failed!
You might need to modify the include and library search paths by editing
QMAKE_INCDIR_OPENGL[_ES2], QMAKE_LIBDIR_OPENGL[_ES2] and QMAKE_LIBS_OPENGL[_ES2]
in the mkspec for your platform.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* the original goal was to keep the default PACKAGECONFIG as minimal
as possible, but I think it's time to enable this
* most builds probably have this enabled anyway because of other dependencies
* new qtbase also shows a warning when it's disabled:
WARNING: Accessibility disabled. This configuration of Qt is unsupported.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* with new Qt, qtbase fails to build with x11 DISTRO_FEATURES
ERROR: Feature 'xcb-xlib' was enabled, but the pre-condition 'features.xlib && libs.xcb_xlib' failed.
Trying source 0 (type makeSpec) of library xlib ...
None of [libXext.so libXext.a] found in [] and global paths.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
OE-Core sets -mcpu option, which is equivalent to -march and -mtune
combination. Therefore don't set -march and -mtune in chromium.
Signed-off-by: Johannes Pointner <johannes.pointner@br-automation.com>
When staging the sdk, the following error is seen:
sed: can't read <path-to-work>/sdk/image/usr/local/oecore-x86_64/sysroots/aarch64-oe-linux/usr/bin/qt.conf: No such file or directory
because the qt.conf file moved from /usr/bin/qt.conf to
/usr/bin/qt5/qt.conf
This change locates the qt.conf file during pkg_postinst using the
OE_QMAKE_PATH_BINS variable, just as when the file is created.
* it was fixed in:
5be2654885
* but then when upgrading to 5.12.3 from meta-qt5/qtwebengine I've accidentally overwritten
this one with the older version in:
e2707a016c
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* allow to disable this completely with
QTWAYLAND_INSTALL_PRIVATE_HEADERS_MANUALLY
e.g. in case you already have your own bbappend resolving this
differently
* use SHRT_VER variable and allow to change it in .bbappend
e.g. in webOS we have different version with different format
without "+git" and 5.11.3-2 ended in upstream_pv which caused
do_install to fail because
${D}${includedir}/QtWaylandClient/5.11.3-2
doesn't exist, split the PV by + as well - to cover both schemes
and allow users to set SHRT_VER to something else if they have
even weirder PV
* install the QtCompositor headers in the same way as QtWaylandClient
we have custom compositor and with 5.11 it was failing to build
because of missing headers, so I had this in .bbappend already
(I thought it was only our issue, because we were using 5.4 based
QtWayland with 5.11, but the same happends with 5.6 based one and
probably newer as well (I don't know what qtwayland version Andreas
was using when first sending the previous qtwayland patch).
* with 5.4 QtWayland and 5.11, I've updated sync.profile with
%inject_headers and @private_headers
built even with this sync.profile change the syncqt.pl in do_install
doesn't install these 5.4 specific profile headers and qtwayland-webos
and luna-surfacemanager fail to build.
This is the diff between:
recipe-sysroot-native/usr/bin/syncqt.pl -version 4.5.2 -showonly
with Qt 5.6 and 5.11
@@ -1,6 +1,5 @@
-<srcbase> = BUILD/work/qemux86-webos-linux/qtwayland/5.4.2-119-r0/git
-<bldbase> = BUILD/work/qemux86-webos-linux/qtwayland/5.4.2-119-r0/git
-<outbase> = BUILD/work/qemux86-webos-linux/qtwayland/5.4.2-119-r0/git
+<srcbase> = BUILD/work/qemux86-webos-linux/qtwayland/5.4.2-119-r0/git
+<outbase> = BUILD/work/qemux86-webos-linux/qtwayland/5.4.2-119-r0/git
pmtrace_qtwaylandclient_provider.h [QtWaylandClient]
qtwaylandclienttracer.h [QtWaylandClient]
qwaylandabstractdecoration_p.h [QtWaylandClient]
@@ -34,34 +33,6 @@
qwaylandwlshellsurface_p.h [QtWaylandClient]
qwaylandxdgshell_p.h [QtWaylandClient]
qwaylandxdgsurface_p.h [QtWaylandClient]
-qwayland-hardware-integration.h [QtWaylandClient]
-qwayland-output-extension.h [QtWaylandClient]
-qwayland-qt-windowmanager.h [QtWaylandClient]
-qwayland-qtkey-extension.h [QtWaylandClient]
-qwayland-server-buffer-extension.h [QtWaylandClient]
-qwayland-sub-surface-extension.h [QtWaylandClient]
-qwayland-surface-extension.h [QtWaylandClient]
-qwayland-text.h [QtWaylandClient]
-qwayland-text-input-unstable-v2.h [QtWaylandClient]
-qwayland-touch-extension.h [QtWaylandClient]
-qwayland-wayland.h [QtWaylandClient]
-qwayland-windowmanager.h [QtWaylandClient]
-qwayland-xdg-shell-unstable-v6.h [QtWaylandClient]
-qwayland-xdg-shell.h [QtWaylandClient]
-wayland-hardware-integration-client-protocol.h [QtWaylandClient]
-wayland-output-extension-client-protocol.h [QtWaylandClient]
-wayland-qt-windowmanager-client-protocol.h [QtWaylandClient]
-wayland-qtkey-extension-client-protocol.h [QtWaylandClient]
-wayland-server-buffer-extension-client-protocol.h [QtWaylandClient]
-wayland-sub-surface-extension-client-protocol.h [QtWaylandClient]
-wayland-surface-extension-client-protocol.h [QtWaylandClient]
-wayland-text-client-protocol.h [QtWaylandClient]
-wayland-text-input-unstable-v2-client-protocol.h [QtWaylandClient]
-wayland-touch-extension-client-protocol.h [QtWaylandClient]
-wayland-wayland-client-protocol.h [QtWaylandClient]
-wayland-windowmanager-client-protocol.h [QtWaylandClient]
-wayland-xdg-shell-client-protocol.h [QtWaylandClient]
-wayland-xdg-shell-unstable-v6-client-protocol.h [QtWaylandClient]
qwaylandclientbufferintegration_p.h [QtWaylandClient]
qwaylandclientbufferintegrationfactory_p.h [QtWaylandClient]
qwaylandclientbufferintegrationplugin_p.h [QtWaylandClient]
@@ -84,38 +55,6 @@
SYMBOL: QWaylandEglWindow
qwaylandglcontext.h [QtWaylandClient]
SYMBOL: QWaylandGLContext
-qwayland-server-wayland.h [QtCompositor]
-qwayland-server-hardware-integration.h [QtCompositor]
-qwayland-server-input-method.h [QtCompositor]
-qwayland-server-ivi-application.h [QtCompositor]
-qwayland-server-output-extension.h [QtCompositor]
-qwayland-server-qt-windowmanager.h [QtCompositor]
-qwayland-server-qtkey-extension.h [QtCompositor]
-qwayland-server-server-buffer-extension.h [QtCompositor]
-qwayland-server-sub-surface-extension.h [QtCompositor]
-qwayland-server-surface-extension.h [QtCompositor]
-qwayland-server-text.h [QtCompositor]
-qwayland-server-text-input-unstable-v2.h [QtCompositor]
-qwayland-server-touch-extension.h [QtCompositor]
-qwayland-server-windowmanager.h [QtCompositor]
-qwayland-server-xdg-shell-unstable-v6.h [QtCompositor]
-qwayland-server-xdg-shell.h [QtCompositor]
-wayland-hardware-integration-server-protocol.h [QtCompositor]
-wayland-input-method-server-protocol.h [QtCompositor]
-wayland-ivi-application-server-protocol.h [QtCompositor]
-wayland-output-extension-server-protocol.h [QtCompositor]
-wayland-qt-windowmanager-server-protocol.h [QtCompositor]
-wayland-qtkey-extension-server-protocol.h [QtCompositor]
-wayland-server-buffer-extension-server-protocol.h [QtCompositor]
-wayland-sub-surface-extension-server-protocol.h [QtCompositor]
-wayland-surface-extension-server-protocol.h [QtCompositor]
-wayland-text-input-unstable-v2-server-protocol.h [QtCompositor]
-wayland-text-server-protocol.h [QtCompositor]
-wayland-touch-extension-server-protocol.h [QtCompositor]
-wayland-wayland-server-protocol.h [QtCompositor]
-wayland-windowmanager-server-protocol.h [QtCompositor]
-wayland-xdg-shell-server-protocol.h [QtCompositor]
-wayland-xdg-shell-unstable-v6-server-protocol.h [QtCompositor]
pmtrace_qtwayland_provider.h [QtCompositor]
qtwaylandtracer.h [QtCompositor]
qwaylandbufferref.h [QtCompositor]
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* like xlib configure test in qtbase fails to link with gold when full path to libm is being used:
| linking ../../../../../plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so
| /OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/qtwayland/5.12.3+gitAUTOINC+bcdc00bcdc-r0/recipe-sysroot-native/usr/bin/x86_64-oe-linux/../../libexec/x86_64-oe-linux/gcc/x86_64-oe-linux/8.3.0/ld: error: cannot open /lib/libm.so.6: No such file or directory
| /OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/qtwayland/5.12.3+gitAUTOINC+bcdc00bcdc-r0/recipe-sysroot-native/usr/bin/x86_64-oe-linux/../../libexec/x86_64-oe-linux/gcc/x86_64-oe-linux/8.3.0/ld: error: cannot open /usr/lib/libmvec_nonshared.a: No such file or directory
| /OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/qtwayland/5.12.3+gitAUTOINC+bcdc00bcdc-r0/recipe-sysroot-native/usr/bin/x86_64-oe-linux/../../libexec/x86_64-oe-linux/gcc/x86_64-oe-linux/8.3.0/ld: error: cannot open /lib/libmvec.so.1: No such file or directory
| collect2: error: ld returned 1 exit status
| Makefile:83: recipe for target '../../../../../plugins/wayland-graphics-integration-client/libqt-plugin-wayland-egl.so' failed
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* be aware that in 3 qt* project the v5.12.3 tag wasn't created yet:
qtknx_git.bb:# v5.12.3 tag wasn't created yet
qtmqtt_git.bb:# v5.12.3 tag wasn't created yet
qtopcua_git.bb:# v5.12.3 tag wasn't created yet
* and qttools, qt3d, qtremoteobjects v5.12.3 tag isn't in 5.12 branch
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* enabling xlib in x86_64 build was failing with:
ERROR: Feature 'xcb-xlib' was enabled, but the pre-condition 'features.xlib && libs.xcb_xlib' failed.
* the root cause is linking with full path libm.so in my case:
/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/qtbase/5.12.3+gitAUTOINC+b527725766-r0/recipe-sysroot/usr/lib/libm.so
which with gold fails with:
/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/qtbase/5.12.3+gitAUTOINC+b527725766-r0/recipe-sysroot-native/usr/bin/x86_64-oe-linux/../../libexec/x86_64-oe-linux/gcc/x86_64-oe-linux/8.3.0/ld: error: cannot open /lib/libm.so.6: No such file or directory
/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/qtbase/5.12.3+gitAUTOINC+b527725766-r0/recipe-sysroot-native/usr/bin/x86_64-oe-linux/../../libexec/x86_64-oe-linux/gcc/x86_64-oe-linux/8.3.0/ld: error: cannot open /usr/lib/libmvec_nonshared.a: No such file or directory
/OE/build/oe-core/tmp-glibc/work/core2-64-oe-linux/qtbase/5.12.3+gitAUTOINC+b527725766-r0/recipe-sysroot-native/usr/bin/x86_64-oe-linux/../../libexec/x86_64-oe-linux/gcc/x86_64-oe-linux/8.3.0/ld: error: cannot open /lib/libmvec.so.1: No such file or directory
collect2: error: ld returned 1 exit status
* not linking with libm at all in xcb test makes it pass, or linking
with -lm as before works as well, but to be safe lets disable gold
everywhere until it's resolved in upstream Qt
* also reported in the 5.12.2 upgrade PR:
https://github.com/meta-qt5/meta-qt5/pull/181#issuecomment-484425112
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
After commit 521a85395, Qt uses global search paths to resolve each library
path, but because we are using -no-gcc-sysroot the native libdir is not part
of the search path. Add the native libdir to search path so that we don't
depend on host libraries for locating zlib.
Fixes "ERROR: Feature 'system-zlib' was enabled, but the pre-condition
'libs.zlib' failed."
Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io>
Signed-off-by: Mikko Gronoff <mikko.gronoff@qt.io>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
All 3rdparty libs and includes are now resolved into full filepaths,
which means build paths to the yocto build environment are in module's
prl, pri, pc and cmake files.
Move existing patching from qtbase to the bbclass so that it's applied
to all modules. -L paths are no longer included in the .pc files, remove
unneeded patching for those.
Task-number: QTBUG-72903
Change-Id: Iae5d150593aef153c46aaf8a3ba22fbafcc9b818
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
Reviewed-by: Mikko Gronoff <mikko.gronoff@qt.io>
Signed-off-by: Mikko Gronoff <mikko.gronoff@qt.io>
Switch from the configure script was extended from -openssl to -openssl-{linked,runtime} so that one can select whether to enable ssl library at linking time or runtime (with dlopen()), or letting the build system decide if no flag is specified.
Now with the OPENSSL_LINKING_MODE variable, it is possible to decide which linking mode to be used.
Signed-off-by: Francesco Giancane <francesco.giancane@polito.it>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Use OE_QMAKE_PATH_EXTERNAL_HOST_BINS in Linguist cmake file similarly
to qtbase's cmake files. This fixes usage in external toolchain.
Task-number: QTBUG-73758
Signed-off-by: Samuli Piippo <samuli.piippo@qt.io>
rpath is needed to be able to run qt tools from the sdk without
having the sdk's lib dir explicitly in LD_LIBRARY_PATH or relying
on host libraries. Qt uses relative rpaths, so the build directories
are not used there.
Signed-off-by: Samuli Piippo <samuli.piippo@qt.io>
QMAKE_COMPILER is not meant to be the actual compiler, but a compiler
type (gcc, clang, mingw). For both mkspecs it's already set in the
common includes. Remove wayland and debug settings from the clang
mkspec as they are already removed from the gcc mkspec.
Signed-off-by: Samuli Piippo <samuli.piippo@qt.io>
* linux-oe-g++ won't work use linux-g++ by default
* we doe not cross compile on target
* adjustment are done at postinst to keep build sysroots unmodified
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
