All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] qt5: install headers into /usr/include/qt5
Date: Tue, 24 Dec 2013 08:47:20 +0100	[thread overview]
Message-ID: <20131224084720.55ea41c3@skate> (raw)
In-Reply-To: <1387868037-31734-1-git-send-email-fatih.asici@gmail.com>

Dear Fatih A??c?,

On Tue, 24 Dec 2013 08:53:57 +0200, Fatih A??c? wrote:
> There are places in Qt's source where headers included with the name of
> the module subdirectory (e.g. #include <QtCore/QHash>). Therefore, the
> build system passes the top header directory to the compiler; but this
> results in a error when building host tools since sysroot/usr/include
> directory includes architecture specific system headers.
> 
> In order to prevent this, install all Qt headers into a subdirectory in
> /usr/include.
> 
> Fixes: http://autobuild.buildroot.net/results/4f1/4f16c0b38bdd6e40efcc781c12fae81c0bfabb72/
> 
> Signed-off-by: Fatih A??c? <fatih.asici@gmail.com>

With this change, what does the compilation command line of host tools
look like?

To me, this change seems more like work-arounding a problem in the Qt
build system rather than a real fix.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2013-12-24  7:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-24  6:53 [Buildroot] [PATCH] qt5: install headers into /usr/include/qt5 Fatih Aşıcı
2013-12-24  7:47 ` Thomas Petazzoni [this message]
2013-12-24  8:15   ` Fatih Aşıcı
2013-12-24  8:22     ` Thomas Petazzoni
2013-12-25 17:16 ` 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=20131224084720.55ea41c3@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.