Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] qt5: No SOURCES in qmake created Makefiles
Date: Fri, 28 Jun 2013 11:50:54 +0200	[thread overview]
Message-ID: <20130628115054.745027af@skate> (raw)
In-Reply-To: <51CC44C0.8020509@andin.de>

Dear Andreas Naumann,

On Thu, 27 Jun 2013 15:57:20 +0200, Andreas Naumann wrote:

> 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
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2013-06-28  9:50 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
2013-06-27 13:57         ` Andreas Naumann
2013-06-28  9:50           ` Thomas Petazzoni [this message]

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=20130628115054.745027af@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