Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] qt5tools: disable qdoc (needs qtdeclarative)
Date: Tue, 12 Apr 2016 22:55:06 +0200	[thread overview]
Message-ID: <20160412225506.71fbffe9@gmx.net> (raw)
In-Reply-To: <20160329155101.6517e0aa@gmx.net>

Hello Thomas,

On Tue, 29 Mar 2016 15:51:01 +0200, Peter Seiderer <ps.report@gmx.net> wrote:

> Hello Thomas,
> 
> On Tue, 29 Mar 2016 14:55:43 +0200, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> 
> > 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?
> 
> Will try to submit the conditional compile solution upstream (but not sure
> if the preferred upstream solution would be qdoc without qml support as done
> for the linguist/lupdate tool)...
> 

No (more) need for a upstream patch, the proper solution will be in
the next qttools release: commit 'qdoc: Let qdoc run without QtDeclarative'
from Martin Smith (see [1] and [2])...

Regards,
Peter
 
[1] https://bugreports.qt.io/browse/QTBUG-51676
[2] http://code.qt.io/cgit/qt/qttools.git/commit/?id=2b262fad86ef38a5fa692b4c73e6ec26a5d45a5f


> Regards,
> Peter
> 
> > 
> > Thomas
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

      reply	other threads:[~2016-04-12 20: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
2016-03-29 13:51   ` Peter Seiderer
2016-04-12 20:55     ` Peter Seiderer [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=20160412225506.71fbffe9@gmx.net \
    --to=ps.report@gmx.net \
    --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