From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] qt5: No SOURCES in qmake created Makefiles
Date: Mon, 17 Jun 2013 16:22:13 +0200 [thread overview]
Message-ID: <20130617162213.1fdc7d97@skate> (raw)
In-Reply-To: <51BF198C.2040405@andin.de>
Dear Andreas Naumann,
On Mon, 17 Jun 2013 16:13:32 +0200, Andreas Naumann wrote:
> 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.
> 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?
> 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
next prev parent reply other threads:[~2013-06-17 14:22 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 [this message]
2013-06-17 16:57 ` Charles Krinke
2013-06-18 15:37 ` Andreas Naumann
2013-06-18 17:06 ` Thomas Petazzoni
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=20130617162213.1fdc7d97@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.