linux/meta-qt5.git/classes, branch upstream/master

Convert to new override syntax

2021-08-03T11:38:16+00:00

This is the result of automated script (0.9.0) conversion: oe-core/scripts/contrib/convert-overrides.py . converting the metadata to use ":" as the override character instead of "_". Signed-off-by: Martin Jansa

cmake_qt5: Add correct qtbase DEPENDS

2021-05-31T21:20:52+00:00

Discussion started at [1] To start a proper fix, set qtbase dependencies depending on target. [1] https://github.com/Freescale/meta-freescale/issues/798 Signed-off-by: Andreas Müller Signed-off-by: Martin Jansa

qtbase: Define OE_QMAKE_OBJCOPY for linux-oe-g++

2021-03-02T16:25:12+00:00

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

Allow enabling gui for native and nativesdk

2019-07-15T13:58:40+00:00

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

qmake5_base.bbclass: Don't expand find -name search patterns

2019-05-30T00:37:21+00:00

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

qt5: patch build paths from installed files

2019-04-03T14:10:43+00:00

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 Reviewed-by: Mikko Gronoff Signed-off-by: Mikko Gronoff

qt5: cleanup mkspecs

2019-03-07T23:54:18+00:00

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

qmake5_paths: change the default QT_DIR_NAME to be empty

2018-09-25T09:22:18+00:00

* there aren't many people using qt4 and qt5 in the same image anymore, it's time to stop using this work around and to follow default packaging rules Signed-off-by: Martin Jansa

qt5: remove all references to qtquick1 import path

2018-07-03T18:00:57+00:00

Since qtquick1 recipes have been removed, there is no need to have OE_QMAKE_PATH_IMPORTS anymore. Signed-off-by: Samuli Piippo

qtbase_git: install qt.conf for the target

2017-12-20T08:23:09+00:00

The build-in qmake settings point to the sysroots on the host machine. Running qmake on the target hence errors with: Could not find qmake configuration file linux-oe-g++. Error processing project file So add qt.conf to the target image with the correct locations. Signed-off-by: Jeroen Hofstee Signed-off-by: Martin Jansa