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: QT5_QMAKE spec bug
Date: Thu, 7 Jul 2016 16:53:16 +0200	[thread overview]
Message-ID: <20160707165316.255efa82@free-electrons.com> (raw)
In-Reply-To: <815daf75-807a-f510-bd73-d87e50b72073@stu.hosei.ac.jp>

Hello,

On Thu, 7 Jul 2016 23:31:14 +0900, Akihiko Odaki wrote:

> qtwaylandscanner in qt5wayland, a package I made. Actually it can be 
> built without host-qt5base.

No, it cannot (from the link you pointed) :

#include <QCoreApplication>
#include <QFile>
#include <QXmlStreamReader>

If it builds on your build machine, it's because you have the Qt5
development files installed. But you cannot rely on them being
available on the build machine of every Buildroot user.

> > Using Python and being a Python package are completely different things.
> >
> > The Python package infrastructure is used by Python modules that use
> > distutils or setuptools.
> >
> > But besides that, lots of packages use Python in their build process,
> > even if they are not at all Python modules.  
> 
> Anyway, such building tools have no variables for their pathes?

Not necessarily. The QT5_QMAKE variable exists precisely because some
arguments must be passed to qmake to make it build code for the target.

> >> The variable is not used in Qt packages and they will need to be
> >> modified to use the variable if it is kept. My patches to add a few Qt
> >> packages are also pending. There is no option to keep as they are.  
> >
> > Not sure I understood this part.  
> 
> So actually packages in package/qt5 doesn't use QT5_QMAKE variable.
> 
> $ git grep bin/qmake package/qt5 | wc -l
> 23
> 
> Shouldn't they refer to QT5_QMAKE if it is kept?

Yes, they probably should, indeed.

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

  reply	other threads:[~2016-07-07 14:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28  9:16 [Buildroot] qt5: QT5_QMAKE spec bug Akihiko Odaki
2016-07-06 23:25 ` Akihiko Odaki
2016-07-07  7:29   ` Julien CORJON
2016-07-07 13:55     ` Akihiko Odaki
2016-07-07 14:06       ` Thomas Petazzoni
2016-07-07 14:31         ` Akihiko Odaki
2016-07-07 14:53           ` Thomas Petazzoni [this message]
2016-07-17  2:06           ` Akihiko Odaki
2016-07-24 22:43             ` Akihiko Odaki

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=20160707165316.255efa82@free-electrons.com \
    --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