From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] qt5connectivity: fix examples compile without Qt gui module
Date: Thu, 23 Nov 2017 19:47:11 +0100 [thread overview]
Message-ID: <20171123194711.39475fd9@gmx.net> (raw)
In-Reply-To: <20171122221248.45984b74@windsurf.lan>
Hello Thomas,
On Wed, 22 Nov 2017 22:12:48 +0100, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> On Sat, 18 Nov 2017 21:40:57 +0100, Peter Seiderer wrote:
> > Add upstream suggested patch to fix heartrate-server (needs only
> > core and bluetooth modules).
> >
> > Fixes [1]:
> >
> > make[3]: Entering directory `.../build/qt5connectivity-5.9.2/examples/bluetooth'
> > cd heartrate-server/ && ( test -e Makefile || .../output/host/bin/qmake -o Makefile .../build/qt5connectivity-5.9.2/examples/bluetooth/heartrate-server/heartrate-server.pro ) && /usr/bin/make -f Makefile
> > Project ERROR: Unknown module(s) in QT: gui
> > make[3]: *** [sub-heartrate-server-make_first] Error 3
> > make[3]: Leaving directory `.../build/qt5connectivity-5.9.2/examples/bluetooth'
> >
> > [1] http://autobuild.buildroot.net/results/387a21fe7fc672e5668b0afddc138cbb7197d234
> >
> > Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> > ---
> > ...rtrate-server-needs-only-core-and-bluetoo.patch | 32 ++++++++++++++++++++++
> > 1 file changed, 32 insertions(+)
> > create mode 100644 package/qt5/qt5connectivity/0001-Example-heartrate-server-needs-only-core-and-bluetoo.patch
>
> I've applied to master, but after moving the patch to a 5.9.2
> subfolder. Indeed, the build issue, and therefore the patch, only apply
> to Qt 5.9 and not Qt 5.6.
Arg, sorry for messing it up, thanks for fixing it...
Regards,
Peter
>
> Thanks!
>
> Thomas
prev parent reply other threads:[~2017-11-23 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-18 20:40 [Buildroot] [PATCH v1] qt5connectivity: fix examples compile without Qt gui module Peter Seiderer
2017-11-22 21:12 ` Thomas Petazzoni
2017-11-23 18:47 ` 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=20171123194711.39475fd9@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