| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
| |
This is useful when QMake has CONFIG+=separate_debug_info which is often
not during the actual bitbake builds but when using an eSDK produced by
the meta-toolchain-qt5 recipe.
Signed-off-by: Dan Christensen <opello@opello.org>
|
|
|
|
| |
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
|
| |
Signed-off-by: Jani Suonpera <jani.suonpera@qt.io>
Change-Id: I5992e74cf524f9378dab64503345111b1cc159f2
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
| |
The QMAKE_AR value is never empty as it always has at least the
cqs argument. Use the default value if the variable has exactly
one argument. Fixes issue #165.
Signed-off-by: Samuli Piippo <samuli.piippo@qt.io>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
|
|
| |
Linking with -pthread fixes the missing atomic linker failures on riscv64.
Thsi fixes the following linker errors:
qtestcase.h:359: more undefined references to `__atomic_fetch_xor_1' follow
collect2: error: ld returned 1 exit status
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
OE_QMAKE_CFLAGS and OE_QMAKE_CXXFLAGS contain path of the build
host, which is not useful for the target, and can be a potential
security risk.
It looks like the following in the target qmake.conf (actual build host path replaced with $PATH_OF_BUILD_HOST):
isEmpty(QMAKE_CFLAGS): QMAKE_CFLAGS = -O2 -pipe -g -feliminate-unused-debug-types -fmacro-prefix-map=$PATH_OF_BUILD_HOST/qtbase/5.15.0+gitAUTOINC+f6fe4bbab7-r0=/usr/src/debug/qtbase/5.15.0+gitAUTOINC+f6fe4bbab7-r0 -fdebug-prefix-map=$PATH_OF_BUILD_HOST/qtbase/5.15.0+gitAUTOINC+f6fe4bbab7-r0=/usr/src/debug/qtbase/5.15.0+gitAUTOINC+f6fe4bbab7-r0 -fdebug-prefix-map=$PATH_OF_BUILD_HOST/qtbase/5.15.0+gitAUTOINC+f6fe4bbab7-r0/recipe-sysroot= -fdebug-prefix-map=$PATH_OF_BUILD_HOST/qtbase/5.15.0+gitAUTOINC+f6fe4bbab7-r0/recipe-sysroot-native=
-fmacro-prefix-map and -fdebug-prefix-map are therefore removed from
qmake.conf on the target, as these are default options only that can be
overridden any time.
Signed-off-by: Mingde (Matthew) Zeng <matthew.zeng@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
| |
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
|
|
|
|
|
|
|
|
|
| |
* https://www.qt.io/blog/qt-5.15-released
* continue to use latest revision in 5.15 (and 80-based) branch for
qtwebengine, because we were already using newer than v5.15.0 revision
and some of those fixes are needed for master (e.g. for build with gcc-10)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
| |
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
|
|
|
|
| |
* use latest revisions in 5.15 branches
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
| |
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
| |
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
| |
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
| |
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
| |
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
| |
* removed from qtbase in:
commit 60588e1a5dd9b10803e078c741271cbe5713a51b
Author: Gatis Paeglis <gatis.paeglis@qt.io>
Date: Tue Feb 19 10:09:19 2019 +0100
3rdparty: remove xcb libs and bump minimal required version to 1.11
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
| |
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
|
|
| |
see added patch
Signed-off-by: Nicola Lunghi <nick83ola@gmail.com>
|
|
|
|
| |
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
|
|
|
|
| |
This forces using the yocto provided package instead
of the one in qtbase/src/3rdparty.
Signed-off-by: Samuli Piippo <samuli.piippo@qt.io>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
|
|
| |
maintenance
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
| |
Signed-off-by: Samuli Piippo <samuli.piippo@qt.io>
|
|
|
|
|
|
| |
Ensure py3 is used during build
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
| |
time element is deprecated on new input_event structure in kernel's
input.h
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
| |
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
| |
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
|
|
|
|
| |
Conversions between float and half are only available when the
taraget has the half-precision extension. Guard these intrinsics
accordingly
Signed-off-by: Khem Raj <raj.khem@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 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>
|
|
|
|
|
|
|
|
|
|
| |
* 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>
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
| |
* 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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Recently pseudo changed to not support reanameeat2 as glibc wrapper [1]. This
causes massive failures at do_install [2] on qtbase.
To work around tell Qt build configuration not to use ranameat2 independent
of glibc version.
Target qtbase does not require this adjustment - there is no pseudo on target.
[1] https://git.openembedded.org/openembedded-core/commit/?id=0fb257121b68f38b40c078150db8f7d0979b7ea5
[2] https://github.com/meta-qt5/meta-qt5/issues/187
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
|
|
|
|
|
|
| |
github.com/meta-qt5 forks
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>
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
mkspecs are not part of qtbase-tools
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
|
|
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
|
| |
* 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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Certain portions of qtwebengine build involves building native tools
using host compiler/linker, this however currently uses gcc and when we
build with clang to compile the target pieces, chromium configures for
clang and rightly so, but then does not have a way to define flags for
host and target separately, and it ends up supplying same flags for both
host and target builds, the trouble is that the options between clang
and gcc are not always same in some cases, they dont understand each
others options. So build starts to fail due to these errors about
unknown cmdline options.
This makes sure we inject CC_host, CXX_host, LD_host into qmake.conf so
they can be used in such packages
We use clang to do host builds when TOOLCHAIN = "clang" is used
otherwise default to gcc as it was the case
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
|
|
|
|
| |
Update PACKAGECONFIG_KDE to ensure that all required packages are
enabled.
Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
|
|
|
|
|
|
| |
* the patches were renamed, but I forgot to amend the SRC_URI modifications
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
|
|
|
|
|
|
| |
See
http://errors.yoctoproject.org/Errors/Details/213681/
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|