From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] qt5: No SOURCES in qmake created Makefiles
Date: Tue, 18 Jun 2013 19:06:56 +0200 [thread overview]
Message-ID: <20130618190656.228e7658@skate> (raw)
In-Reply-To: <51C07EB6.4080003@andin.de>
Dear Andreas Naumann,
On Tue, 18 Jun 2013 17:37:26 +0200, Andreas Naumann wrote:
> 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.
Ah, ah, this is interesting. I'll try to reproduce and let you know
what I find.
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-06-18 17:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 14:13 [Buildroot] qt5: No SOURCES in qmake created Makefiles Andreas Naumann
2013-06-17 14:22 ` Thomas Petazzoni
2013-06-17 16:57 ` Charles Krinke
2013-06-18 15:37 ` Andreas Naumann
2013-06-18 17:06 ` Thomas Petazzoni [this message]
2013-06-27 13:57 ` Andreas Naumann
2013-06-28 9:50 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130618190656.228e7658@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox