linux/meta-qt5.git/classes, branch krogoth

cmake_qt5.bbclass: add qtbase-native to DEPENDS

2017-02-20T13:40:16+00:00

When building with recipe-specific-sysroot's, qmake can't be found: | CMake Error at WORKDIR/recipe-sysroot/usr/lib/cmake/Qt5Core/Qt5CoreConfig.cmake:32 (message): | The imported target Qt5::Core references the file | | WORKDIR/recipe-sysroot-native/usr/bin/qt5/qmake | | but this file does not exist. Possible reasons include: | | * The file was deleted, renamed, or moved to another location. | | * An install or uninstall procedure did not complete successfully. | | * The installation package was faulty and contained | | WORKDIR/recipe-sysroot/usr/lib/cmake/Qt5Core/Qt5CoreConfigExtras.cmake | | but not all the files it references. | | Call Stack (most recent call first): | WORKDIR/recipe-sysroot/usr/lib/cmake/Qt5Core/Qt5CoreConfigExtras.cmake:6 (_qt5_Core_check_file_exists) | WORKDIR/recipe-sysroot/usr/lib/cmake/Qt5Core/Qt5CoreConfig.cmake:163 (include) | WORKDIR/recipe-sysroot/usr/lib/cmake/Qt5/Qt5Config.cmake:31 (find_package) | CMakeLists.txt:56 (find_package) | This is solved by adding qtbase-native to the exported DEPENDS. Signed-off-by: Anders Darander Signed-off-by: Martin Jansa

cmake_qt5.bbclass: when using _prepend don't forget to add space at the end

2016-08-05T09:12:12+00:00

Previous commit aacd63f10dd58acf7bf6138e2f4734e37dcf0420 introduced a bug by using _prepend w/o a space at the end, resulting in corrupted EXTRA_OEMAKE variable in packages that inherit cmake_qt5.bbclass. Signed-off-by: Denys Dmytriyenko Signed-off-by: Martin Jansa

cmake_qt5: prepend the Qt5 specific CMake variables to EXTRA_OECMAKE

2016-06-07T18:10:21+00:00

Using the prepend function instead of "=+" makes sure the variables are set even if the user overrides EXTRA_OECMAKE with "=" instead of just appending to it. Prepending also allows overriding because later arguments take precedence ever earlier ones in CMake. Signed-off-by: Pascal Bach Signed-off-by: Martin Jansa

qmake5_base: use remove-libtool bbclass

2016-04-20T08:50:50+00:00

* this requires latest oe-core (Yocto 2.1), if you want to use latest meta-qt5 with older oe-core, you need to backport this bbclass and more importantly don't forget to provide EXTRA_CONF_PACKAGECONFIG Signed-off-by: Martin Jansa

qmake5_base: delete *.la files

2016-02-17T21:55:37+00:00

* they reference workdir and trip sanity check: ERROR: QA Issue: libQt5Sql.la failed sanity test (workdir) in path qtbase/5.5.99+5.6.0-alpha1+gitAUTOINC+f7f4dde80e-r0/sysroot-destdir//usr/lib [la] * I'm intentionally not using remove-libtool.bbclass recently added to oe-core, because many people combine newer meta-qt5 with older oe-core and can be missing this bbclass, I've pending patch to migrate this to remove-libtool.bbclass, will probably merge it after 2.1 or 2.2 release. Signed-off-by: Martin Jansa

cmake_qt5.bbclass: add DEPENDS to qtbase

2015-12-15T15:46:42+00:00

All packages using this class need it and it is too easy for developers to miss and leave race conditions into builds. Signed-off-by: Mikko Rapeli Signed-off-by: Martin Jansa

qt5: upgrade to latest revision in 5.6 branch (5.6.0-alpha1+)

2015-11-11T12:24:53+00:00

Signed-off-by: Martin Jansa

qttools: fix cmake usage of linguist tools

2015-10-15T15:10:36+00:00

Without this, Qt5LinguistTools/Qt5LinguistToolsConfig.cmake would attempt to locate lrelease and lupdate under prefix, even while we were cross-compiling and prefix points at the native system's root dirs. Signed-off-by: Cody P Schafer Signed-off-by: Martin Jansa

qmake5_paths, qtbase: add OE_QMAKE_PATH_QT_FONTS

2015-09-29T15:41:59+00:00

* people using fontconfig may want to change this path to ${datadir}/fonts, it was set to OE_QMAKE_PATH_LIBS in commit 1fdab229df6000eb52ac721a3ff4cdd218a0c308 to follow mkspecs/features/qpa/genericunixfontdatabase.prf fonts.path = $$[QT_INSTALL_LIBS]/fonts Signed-off-by: Martin Jansa

Remove double slash when QT_DIR_NAME is empty

2015-09-21T09:56:52+00:00

When `QT_DIR_NAME` is defined as an empty string (default is "qt5"), package.bbclass will throw lots of QA warnings because now the paths contain double slashes ("//"). We can address these warnings by explicitly defining a slash in the variable itself. Signed-off-by: Adam YH Lee Signed-off-by: Martin Jansa