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:06:36 +0200 [thread overview]
Message-ID: <20160707160636.505b2da4@free-electrons.com> (raw)
In-Reply-To: <c7b1de47-7662-cd58-def1-f82fd70aa533@stu.hosei.ac.jp>
Hello,
On Thu, 7 Jul 2016 22:55:36 +0900, Akihiko Odaki wrote:
> I think those packages are not meant to be built for the host.
QT5_QMAKE is a variable meant to built qmake-based packages for the
target. It has never been intended to build qmake-based packages for
the host.
Which qmake-based package do you need to build for host? Notice that we
do not build qt5 for the host, so in order to build qmake-based
packages for the host, you would first have to create a host-qt5base
package, which is going to cause a lot of problems down the road.
> > Python and others already have their own infrastructures so they
> don't need this kind of stuff.
>
> You mean package/pkg-*.mk by the infrastructures? Many packages
> depending on Python don't use package/pkg-python.mk and specify the path
> in their -.mk.
>
> $ git grep bin/python | wc -l
> 93
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.
> 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.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-07-07 14:06 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 [this message]
2016-07-07 14:31 ` Akihiko Odaki
2016-07-07 14:53 ` Thomas Petazzoni
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=20160707160636.505b2da4@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