Overwrite and extend do_install_ptest for qtdeclarative. It fixes
runtime errors:
| FAIL! : TestQmllint::initTestCase() '!m_dataDirectory.isEmpty()'
returned FALSE. ('data' directory not found)
With this change, more tests have been run and the results are better:
passed: 993 -> 2318
failed: 182 -> 113
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* fixes:
WARNING: meta-qt5/recipes-qt/qt5/qtbase-native_git.bb: QA Issue: qtbase-native: native/nativesdk class is not inherited last, this can result in unexpected behaviour. [native-last]
WARNING: meta-qt5/recipes-qt/qt5/nativesdk-qtbase_git.bb: QA Issue: nativesdk-qtbase: native/nativesdk class is not inherited last, this can result in unexpected behaviour. [native-last]
WARNING: meta-qt5/recipes-qt/packagegroups/nativesdk-packagegroup-qt5-toolchain-host.bb: QA Issue: nativesdk-packagegroup-qt5-toolchain-host: native/nativesdk class is not inherited last, this can result in unexpected behaviour. [native-last]
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Current Qtwebkit configuration is debug build by default.
Change it to release build to have better performance.
Change-Id: Ib5e10bfd62edf79ddc304332ff10fdbe3abf58f0
Reviewed-by: Chenxi Mao <chenxi.mao2013@gmail.com>
Reviewed-by: Konstantin Tokarev <annulen@yandex.ru>
it depends on qtwebengine which inturn depends on chromium which inturn
depends on python2 during build. So lets disable it when meta-python2 is
not used until such time when chromium does not need python2
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>
Old version no longer available through riverbankcomputing.com.
Update to 5.15.1 and download the package sources using pypi class.
Signed-off-by: Daniel Gomez <daniel@qtec.com>
* patch was taken from meta-browser. The only modification done was adding the
error seen
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* Fixes:
| ERROR at //third_party/icu/BUILD.gn:10:1: Unable to load "<...>/qtwebengine/5.15.0+gitAUTOINC+f526855509_7b2f027ea8-r0/git/src/3rdparty/chromium/v8/snapshot_toolchain.gni".
| import("//v8/snapshot_toolchain.gni")
| ^-----------------------------------
| See //url/BUILD.gn:97:15: which caused the file to be included.
| deps += [ "//third_party/icu" ]
| ^------------------
| Project ERROR: GN run error!
* Discussion found at [1]
* Build tested with/without icu in PACKAGECONFIG
[1] https://github.com/meta-qt5/meta-qt5/pull/351
Signed-off-by: Andreas Müller <schnitzeltony@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>
Actually these belong to packagegroup-qt5-toolchain-target but:
* qtwebengine is a resource consuming build monster and not mandatory for
everybody's qt-toolchain
* as far as I tested qtwebengine does not build for clang - so reduce impact
for people using clang-toolchain
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
Without cmake qt-creator is not of much use - most projects use cmake these
days and as far as I can remember qt will move to build with cmake.
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
Test case:
* meta-clang in layers
* gcc toolchain
* build qttools with PACKAGECONFIG[clang] enabled to get (native) help tools.
After setting clang PACKAGECONFIG at qttools, qt5-creator builds failed due to
linker errors: Linker tried to link against native clang tools. Avoid that in
the same way as clang-toolchain did but use PACKAGECONFIG.
* clang-toolchain builds remain unchanged
* a hint was dropped in the recipe to support users failing for same issue
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
Am working on recipes for kdevelop and musescore. These require native help
tools - at least because cmake configs reference them.
* Have tried other - patch-less - ways to achieve this without success
* Tested multiple combinations with and without clang in PACKAGECONFIG * gcc/clang
toolchain with expected result: For clang set, native tools are build for
clang misssing tools are not build.
* Target build remained unchanged because it was buildung help tools with clang
in PACKAGECONFIG
* Tried also to add the patch to nativesdk but help tools were not build.
Stopped further investigation - that is not a use case for me - sorry
Note for clang-toolchain users (confused me a bit - now it's obvious): For
qttools-native clang has to be set explicitly in PACKAGECONFIG, otherwise
native help tools are not build (same as behaviour as before).
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
In order to more easily use some oFono bits like (multi)-sim and network management in QML, let's add libqofonoext as well.
Signed-off-by: Herman van Hazendonk <github.com@herrie.org>
ERROR: do_rootfs: Postinstall scriptlets of ['maliit-framework-qt5'] have failed. If the intention is to defer them to first boot,
then please place them into pkg_postinst_ontarget_${PN} ().
Deferring to first boot via 'exit 1' is no longer supported.
Signed-off-by: Gianfranco Costamagna <costamagnagianfranco@yahoo.it>
Signed-off-by: Gianfranco Costamagna <gianfranco.costamagna@abinsula.com>
Signed-off-by: Gianfranco Costamagna <locutusofborg@debian.org>
Upstream finally supports multilib properly, so bumping our version and dropping the patch for this.
Signed-off-by: Herman van Hazendonk <github.com@herrie.org>
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>
- use bundled one for native/v8 internal builds
Complete system ICU library using requires ICU dev package be installed
on host. Enabling dependency on native package is not enough due to V8
hosttools toolchain. V8 toolchain is not using native sysroot, only
a host packages. On the other hand webenegine does not produce external
native artifacts. So external system ICU linking is not needed.
Signed-off-by: Andrej Valek <andrej.valek@siemens.com>
