From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] package/qt5/qt5scxml: needs qt5declarative package
Date: Wed, 27 Dec 2017 23:17:00 +0100 [thread overview]
Message-ID: <20171227231700.4b3cfadf@gmx.net> (raw)
In-Reply-To: <20171227224206.37fef60a@windsurf.home>
Hello Thomas,
On Wed, 27 Dec 2017 22:42:06 +0100, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> On Wed, 27 Dec 2017 22:26:16 +0100, Peter Seiderer wrote:
>
>
> > > diff --git a/package/qt5/qt5scxml/Config.in b/package/qt5/qt5scxml/Config.in
> > > index 4ae6a5b..469bdc1 100644
> > > --- a/package/qt5/qt5scxml/Config.in
> > > +++ b/package/qt5/qt5scxml/Config.in
> > > @@ -1,7 +1,9 @@
> > > config BR2_PACKAGE_QT5SCXML
> > > bool "qt5scxml"
> > > depends on BR2_PACKAGE_QT5_VERSION_LATEST
> > > + depends on BR2_PACKAGE_QT5_JSCORE_AVAILABLE
> >
> > Better:
> > depends on BR2_PACKAGE_QT5_JSCORE_AVAILABLE # qt5declarative
>
> True.
>
> > > select BR2_PACKAGE_QT5BASE
> >
> > Not sure if an explicit select is needed, but qt5declarative selects the following:
> >
> > select BR2_PACKAGE_QT5BASE_GUI # qt5declarative
> > select BR2_PACKAGE_QT5XMLPATTERNS # qt5declarative
>
> So why does your patch also selects them, if they are already
> implicitly selected by qt5declarative ?
Thanks for the reasoning, but one more question: with this logic
the above 'select BR2_PACKAGE_QT5BASE' could be removed (but the
below dependency on qt5base without the corresponding select seems
ugly)?
>
> > diff --git a/package/qt5/qt5scxml/qt5scxml.mk b/package/qt5/qt5scxml/qt5scxml.mk
> > index 4b1f97973d..3deef99aaf 100644
> > --- a/package/qt5/qt5scxml/qt5scxml.mk
> > +++ b/package/qt5/qt5scxml/qt5scxml.mk
> > @@ -7,7 +7,7 @@
> > QT5SCXML_VERSION = $(QT5_VERSION)
> > QT5SCXML_SITE = $(QT5_SITE)
> > QT5SCXML_SOURCE = qtscxml-opensource-src-$(QT5SCXML_VERSION).tar.xz
> > -QT5SCXML_DEPENDENCIES = qt5base
> > +QT5SCXML_DEPENDENCIES = qt5base qt5xmlpatterns qt5declarative
>
> True for qt5declarative. But for qt5xmlpatterns? Is it directly used by
> qt5scxml? If not, then adding it is not necessary, as qt5declarative
> already has a dependency on it.
>
> Could you send a follow-up patch doing the remaining fixes?
O.k, will do...
Regards,
Peter
>
> Thanks a lot!
>
> Thomas
next prev parent reply other threads:[~2017-12-27 22:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-27 21:07 [Buildroot] [git commit] package/qt5/qt5scxml: needs qt5declarative package Thomas Petazzoni
2017-12-27 21:26 ` Peter Seiderer
2017-12-27 21:42 ` Thomas Petazzoni
2017-12-27 22:17 ` Peter Seiderer [this message]
2017-12-27 22:27 ` Thomas Petazzoni
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=20171227231700.4b3cfadf@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