qt5: No SOURCES in qmake created Makefiles
Hi Thomas,
when using qt4 up till now I used the output/host/usr/bin/qmake to prepare out of tree projects/examples for compilation. Worked like a charm and i was very happy being able to use a consistent toolchain for that.
However when I try the same with the qt5 qmake binary, the the SOURCES of the .pro file (and maybe other options) dont make it into the Makefile. So running make results in "Nothing to do for target first". Have you or anybody else successfully compiled out of tree qt5 applications and if so how? Or, are there any examples on writing a package for qt5 applications?
thanks and regards,
Andreas
Dear Andreas Naumann,
Quoted 4 lines · Andreas Naumann
when using qt4 up till now I used the output/host/usr/bin/qmake to prepare out of tree projects/examples for compilation. Worked like a charm and i was very happy being able to use a consistent toolchain for that.
Using output/host/usr/bin/qmake is indeed the correct way and is supposed to do the right thing in terms of toolchain and flags and so on.
Quoted 3 lines
However when I try the same with the qt5 qmake binary, the the SOURCES of the .pro file (and maybe other options) dont make it into the
Makefile.
Can you clarify exactly what happens?
Quoted 4 lines
So running make results in "Nothing to do for target first". Have you or anybody else successfully compiled out of tree qt5 applications and if so how? Or, are there any examples on writing a package for qt5 applications?
It has been a few months now, but when I did the Qt5 packaging, I'm pretty sure I did test a sample Hello World application that was compiled "out of tree" (i.e not a Buildroot package) with output/host/usr/bin/qmake. There may have been some regressions/issues in the mean time, though.
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
Dear Andreas:
I am using a similar recipe with Qt-5.0.2 as with Qt-4.8.2 for out of tree application builds, that is, exporting the PATH prefix to output/host/usr/bin/qmake and now specifying the mkspec in mkspec/devices/linux-buildroot-g++, so I can confirm this works and is both finding the Qt5 *stuff* and the TI es3 *stuff*.
Now, I am using Wojeich's patch for the mkspec as it is a lot simpler and actually works then the one that brings in the Graphics_SDK, but lets assume that is not your issue.
Charles
Quoted 41 lines · Thomas Petazzoni
Dear Andreas Naumann,
Quoted 4 lines · Andreas Naumann
when using qt4 up till now I used the output/host/usr/bin/qmake to prepare out of tree projects/examples for compilation. Worked like a charm and i was very happy being able to use a consistent toolchain for that.
Using output/host/usr/bin/qmake is indeed the correct way and is supposed to do the right thing in terms of toolchain and flags and so on.
Quoted 3 lines
However when I try the same with the qt5 qmake binary, the the SOURCES of the .pro file (and maybe other options) dont make it into the
Makefile.Can you clarify exactly what happens?
Quoted 4 lines
So running make results in "Nothing to do for target first". Have you or anybody else successfully compiled out of tree qt5 applications and if so how? Or, are there any examples on writing a package for qt5 applications?
It has been a few months now, but when I did the Qt5 packaging, I'm pretty sure I did test a sample Hello World application that was compiled "out of tree" (i.e not a Buildroot package) with output/host/usr/bin/qmake. There may have been some regressions/issues in the mean time, though.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
Signature · 1 line
Charles Krinke
Dear Thomas and Charles
In order to reproduce the issue I used the beaglebone_defconfig, changed to linaro toolchain and activated a minimal qt5 set:
BR2_PACKAGE_QT5=y
BR2_PACKAGE_QT5BASE=y
BR2_PACKAGE_QT5BASE_LICENSE_APPROVED=y BR2_PACKAGE_QT5BASE_GUI=y
BR2_PACKAGE_QT5BASE_WIDGETS=y
BR2_PACKAGE_QT5BASE_LINUXFB=y
BR2_PACKAGE_QT5JSBACKEND=y
Now I have been going back in revisions and find the problem to start exactly when switching to qt 5.0.2 (d6b2bac qt5: bump to 5.0.2). So I have been looking through the release notes
(http://blog.qt.digia.com/blog/2013/04/10/qt-5-0-2-released/) but nothing really rings a bell. But I'm not very knowledgable in the qt build framework.
So Charles, I'm interested in how you still get it working. What do you mean with similar recipe? Do you use the qt-5.0.2 package from buildroot? Which QT5 configs, toolchain, board?
regards
Andreas
Am 17.06.2013 18:57, schrieb Charles Krinke:
Quoted 58 lines
Dear Andreas:
I am using a similar recipe with Qt-5.0.2 as with Qt-4.8.2 for out of tree application builds, that is, exporting the PATH prefix to output/host/usr/bin/qmake and now specifying the mkspec in mkspec/devices/linux-buildroot-g++, so I can confirm this works and is both finding the Qt5 *stuff* and the TI es3 *stuff*.
Now, I am using Wojeich's patch for the mkspec as it is a lot simpler and actually works then the one that brings in the
Graphics_SDK, but lets assume that is not your issue.Charles
Quoted 41 lines · Thomas Petazzoni
Dear Andreas Naumann,
Quoted 4 lines · Andreas Naumann
when using qt4 up till now I used the output/host/usr/bin/qmake to prepare out of tree projects/examples for compilation. Worked like a charm and i was very happy being able to use a consistent toolchain for that.
Using output/host/usr/bin/qmake is indeed the correct way and is supposed to do the right thing in terms of toolchain and flags and so on.
Quoted 3 lines
However when I try the same with the qt5 qmake binary, the the SOURCES of the .pro file (and maybe other options) dont make it into the
Makefile.Can you clarify exactly what happens?
Quoted 4 lines
So running make results in "Nothing to do for target first". Have you or anybody else successfully compiled out of tree qt5 applications and if so how? Or, are there any examples on writing a package for qt5 applications?
It has been a few months now, but when I did the Qt5 packaging, I'm pretty sure I did test a sample Hello World application that was compiled "out of tree" (i.e not a Buildroot package) with output/host/usr/bin/qmake. There may have been some regressions/issues in the mean time, though.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
Dear Andreas Naumann,
Quoted 10 lines · Andreas Naumann
In order to reproduce the issue I used the
beaglebone_defconfig, changed to linaro toolchain and activated a minimal qt5 set:
BR2_PACKAGE_QT5=y
BR2_PACKAGE_QT5BASE=y
BR2_PACKAGE_QT5BASE_LICENSE_APPROVED=y BR2_PACKAGE_QT5BASE_GUI=y
BR2_PACKAGE_QT5BASE_WIDGETS=y
BR2_PACKAGE_QT5BASE_LINUXFB=y
BR2_PACKAGE_QT5JSBACKEND=y
Quoted 6 lines
Now I have been going back in revisions and find the problem to start exactly when switching to qt 5.0.2 (d6b2bac qt5: bump to 5.0.2). So I have been looking through the release notes
(http://blog.qt.digia.com/blog/2013/04/10/qt-5-0-2-released/) but nothing really rings a bell. But I'm not very knowledgable in the qt build framework.
Ah, ah, this is interesting. I'll try to reproduce and let you know what I find.
Thanks,
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com
Hi,
am a little sorry for the fuzz. This worked out to be a non-issue. Seems when using examples from another qt tree, even though absolutely clean within the directory, still build options from the folders above get picked up.
When I copied it away, in my case to /tmp/analogclock/, compiling with buildroots qmake from 5.0.2 works just fine.
cheers,
Andreas
Am 18.06.2013 19:06, schrieb Thomas Petazzoni:
Quoted 28 lines
Dear Andreas Naumann,
Quoted 10 lines · Andreas Naumann
In order to reproduce the issue I used the
beaglebone_defconfig, changed to linaro toolchain and activated a minimal qt5 set:
BR2_PACKAGE_QT5=y
BR2_PACKAGE_QT5BASE=y
BR2_PACKAGE_QT5BASE_LICENSE_APPROVED=y BR2_PACKAGE_QT5BASE_GUI=y
BR2_PACKAGE_QT5BASE_WIDGETS=y
BR2_PACKAGE_QT5BASE_LINUXFB=y
BR2_PACKAGE_QT5JSBACKEND=yQuoted 6 lines
Now I have been going back in revisions and find the problem to start exactly when switching to qt 5.0.2 (d6b2bac qt5: bump to 5.0.2). So I have been looking through the release notes
(http://blog.qt.digia.com/blog/2013/04/10/qt-5-0-2-released/) but nothing really rings a bell. But I'm not very knowledgable in the qt build framework.Ah, ah, this is interesting. I'll try to reproduce and let you know what I find.
Thanks,
Thomas
Dear Andreas Naumann,
Quoted 6 lines · Andreas Naumann
am a little sorry for the fuzz. This worked out to be a non-issue. Seems when using examples from another qt tree, even though absolutely clean within the directory, still build options from the folders above get picked up.
When I copied it away, in my case to/tmp/analogclock/, compiling with buildroots qmake from 5.0.2 works just fine.
I do reproduce your problem now: when building an example from within the Qt source tree, it fails with "Nothing to do for target first", when copying the source code of the example outside of Qt source tree, the building goes on nicely.
We still should fix this, examples are supposed to build from within the Qt source tree.
Best regards,
Thomas
Signature · 4 lines
Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com