<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-qt5.git/classes, branch upstream/dunfell</title>
<subtitle>Mirror of https://code.qt.io/cgit/yocto/meta-qt5.git</subtitle>
<id>https://git.enea.com/cgit/linux/meta-qt5.git/atom?h=upstream%2Fdunfell</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-qt5.git/atom?h=upstream%2Fdunfell'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-qt5.git/'/>
<updated>2019-07-15T13:58:40+00:00</updated>
<entry>
<title>Allow enabling gui for native and nativesdk</title>
<updated>2019-07-15T13:58:40+00:00</updated>
<author>
<name>Samuli Piippo</name>
<email>samuli.piippo@qt.io</email>
</author>
<published>2019-05-31T11:49:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-qt5.git/commit/?id=8da88b098fae46e13cd7cbaf8d65dd0e99b4e0e5'/>
<id>urn:sha1:8da88b098fae46e13cd7cbaf8d65dd0e99b4e0e5</id>
<content type='text'>
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 &lt;samuli.piippo@qt.io&gt;
</content>
</entry>
<entry>
<title>qmake5_base.bbclass: Don't expand find -name search patterns</title>
<updated>2019-05-30T00:37:21+00:00</updated>
<author>
<name>Florent Revest</name>
<email>revestflo@gmail.com</email>
</author>
<published>2019-05-27T20:02:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-qt5.git/commit/?id=46c87e060dfd0e6cf132a330eab8cbefddde215d'/>
<id>urn:sha1:46c87e060dfd0e6cf132a330eab8cbefddde215d</id>
<content type='text'>
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 &lt;revestflo@gmail.com&gt;
</content>
</entry>
<entry>
<title>qt5: patch build paths from installed files</title>
<updated>2019-04-03T14:10:43+00:00</updated>
<author>
<name>Samuli Piippo</name>
<email>samuli.piippo@qt.io</email>
</author>
<published>2019-01-10T14:18:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-qt5.git/commit/?id=adf7f605872f246b692fd9628af26505f6e9c485'/>
<id>urn:sha1:adf7f605872f246b692fd9628af26505f6e9c485</id>
<content type='text'>
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 &lt;oswald.buddenhagen@gmx.de&gt;
Reviewed-by: Mikko Gronoff &lt;mikko.gronoff@qt.io&gt;
Signed-off-by: Mikko Gronoff &lt;mikko.gronoff@qt.io&gt;
</content>
</entry>
<entry>
<title>qt5: cleanup mkspecs</title>
<updated>2019-03-07T23:54:18+00:00</updated>
<author>
<name>Samuli Piippo</name>
<email>samuli.piippo@qt.io</email>
</author>
<published>2019-01-08T12:51:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-qt5.git/commit/?id=92c34de4bb11223c059466d3d0690eb763a56102'/>
<id>urn:sha1:92c34de4bb11223c059466d3d0690eb763a56102</id>
<content type='text'>
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 &lt;samuli.piippo@qt.io&gt;
</content>
</entry>
<entry>
<title>qmake5_paths: change the default QT_DIR_NAME to be empty</title>
<updated>2018-09-25T09:22:18+00:00</updated>
<author>
<name>Martin Jansa</name>
<email>Martin.Jansa@gmail.com</email>
</author>
<published>2018-09-14T12:35:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-qt5.git/commit/?id=b716195f609de6547cfdfadfd4fd25292a6bbf09'/>
<id>urn:sha1:b716195f609de6547cfdfadfd4fd25292a6bbf09</id>
<content type='text'>
* 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 &lt;Martin.Jansa@gmail.com&gt;
</content>
</entry>
<entry>
<title>qt5: remove all references to qtquick1 import path</title>
<updated>2018-07-03T18:00:57+00:00</updated>
<author>
<name>Samuli Piippo</name>
<email>samuli.piippo@qt.io</email>
</author>
<published>2018-06-27T12:59:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-qt5.git/commit/?id=7faa5d8f39381975a861e3e918789e9f33a079f6'/>
<id>urn:sha1:7faa5d8f39381975a861e3e918789e9f33a079f6</id>
<content type='text'>
Since qtquick1 recipes have been removed, there is no need to have
OE_QMAKE_PATH_IMPORTS anymore.

Signed-off-by: Samuli Piippo &lt;samuli.piippo@qt.io&gt;
</content>
</entry>
<entry>
<title>qtbase_git: install qt.conf for the target</title>
<updated>2017-12-20T08:23:09+00:00</updated>
<author>
<name>Jeroen Hofstee</name>
<email>jhofstee@victronenergy.com</email>
</author>
<published>2017-11-21T09:51:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-qt5.git/commit/?id=3cf0bbb8e1113376d5b5b26ecff362e180a180fd'/>
<id>urn:sha1:3cf0bbb8e1113376d5b5b26ecff362e180a180fd</id>
<content type='text'>
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 &lt;jhofstee@victronenergy.com&gt;
Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
</content>
</entry>
<entry>
<title>qt5: remove use of OE_QMAKE_WAYLAND_SCANNER</title>
<updated>2017-12-20T08:21:17+00:00</updated>
<author>
<name>Samuli Piippo</name>
<email>samuli.piippo@qt.io</email>
</author>
<published>2017-11-10T07:13:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-qt5.git/commit/?id=d27c0199dbe453b3b9af32783f6d15c022f18429'/>
<id>urn:sha1:d27c0199dbe453b3b9af32783f6d15c022f18429</id>
<content type='text'>
This was never defined for nativesdk, which then broke sdk which
had nativesdk-qtwayland included. Rather than add it there, remove
its use everywhere, since it was not adding anything meaningful to
the build.

Signed-off-by: Samuli Piippo &lt;samuli.piippo@qt.io&gt;
Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
</content>
</entry>
<entry>
<title>qt5: use correct HostPrefix</title>
<updated>2017-12-20T08:20:48+00:00</updated>
<author>
<name>Samuli Piippo</name>
<email>samuli.piippo@qt.io</email>
</author>
<published>2017-11-10T06:44:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-qt5.git/commit/?id=70f36ebae41a7f4445d8bc94ded78ba4a04613de'/>
<id>urn:sha1:70f36ebae41a7f4445d8bc94ded78ba4a04613de</id>
<content type='text'>
Different HostPrefix was used when building Qt and in external
SDK's qt.conf. This caused e.g., wrong path in qmodule.pri for
PKG_CONFIG_EXECUTABLE.

Task-number: QTBUG-63097
Signed-off-by: Samuli Piippo &lt;samuli.piippo@qt.io&gt;
Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
</content>
</entry>
<entry>
<title>qtbase: Add OE clang specific mkspecs</title>
<updated>2017-09-05T12:56:02+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2017-09-03T18:10:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-qt5.git/commit/?id=90d4a41621886ae5e738ec8a0b693e88b25d8267'/>
<id>urn:sha1:90d4a41621886ae5e738ec8a0b693e88b25d8267</id>
<content type='text'>
We can not piggy back clang anymore on existing
OE mkspecs since starting 5.9 the configure is
asking compiler for include paths and it needs to
know if platform is clang-linux or g++-linux

Fixes:
ERROR: failed to parse default search paths from compiler output

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
Signed-off-by: Martin Jansa &lt;Martin.Jansa@gmail.com&gt;
</content>
</entry>
</feed>
