From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] qt5tools: disable qdoc (needs qtdeclarative)
Date: Tue, 29 Mar 2016 14:55:43 +0200 [thread overview]
Message-ID: <20160329145543.45f90da8@free-electrons.com> (raw)
In-Reply-To: <1459251925-31678-1-git-send-email-ps.report@gmx.net>
Hello,
On Tue, 29 Mar 2016 13:45:25 +0200, Peter Seiderer wrote:
> Fixes [1]:
>
> Project ERROR: Unknown module(s) in QT: qmldevtools-private
> Makefile:63: recipe for target 'sub-qdoc-qmake_all' failed
>
> [1] http://autobuild.buildroot.net/results/b0a/b0a5641beae14ff79a9d5a628bb41957826eb623
>
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
Thanks, I've applied to fix the build issue, but I would really prefer
a solution that is acceptable upstream. If I remember correctly, you
can do some conditionals in .pro files like "if qtdeclarative is
available, then do this". This way, you could build qdoc if
qtdeclarative is available, and not build it otherwise.
What do you think?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-03-29 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 11:45 [Buildroot] [PATCH v1] qt5tools: disable qdoc (needs qtdeclarative) Peter Seiderer
2016-03-29 12:55 ` Thomas Petazzoni [this message]
2016-03-29 13:51 ` Peter Seiderer
2016-04-12 20:55 ` Peter Seiderer
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=20160329145543.45f90da8@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