From: "Fatih Aşıcı" <fatih.asici@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/6] qt5declarative: add an option for quick module
Date: Sun, 20 Jul 2014 14:33:17 +0300 [thread overview]
Message-ID: <2568185.NtVTRxoxRO@asici> (raw)
In-Reply-To: <20140720120431.45cede42@free-electrons.com>
On Sunday 20 July 2014 12:04:31 Thomas Petazzoni wrote:
> Dear Fatih A??c?,
>
> On Sat, 19 Jul 2014 20:33:25 +0300, Fatih A??c? wrote:
> > diff --git a/package/qt5/qt5declarative/qt5declarative.mk
> > b/package/qt5/qt5declarative/qt5declarative.mk index 472d092..34dd14a
> > 100644
> > --- a/package/qt5/qt5declarative/qt5declarative.mk
> > +++ b/package/qt5/qt5declarative/qt5declarative.mk
> > @@ -35,12 +35,20 @@ define QT5DECLARATIVE_INSTALL_STAGING_CMDS
> >
> > endef
> >
> > ifeq ($(BR2_PREFER_STATIC_LIB),)
> >
> > -define QT5DECLARATIVE_INSTALL_TARGET_LIBS
> > - cp -dpf $(STAGING_DIR)/usr/lib/libQt5Qml*.so.* $(TARGET_DIR)/usr/lib
> > +
> > +ifeq ($(BR2_PACKAGE_QT5DECLARATIVE_QUICK),y)
> > +define QT5DECLARATIVE_INSTALL_TARGET_QUICK_LIBS
> >
> > cp -dpf $(STAGING_DIR)/usr/lib/libQt5Quick*.so.* $(TARGET_DIR)/usr/lib
> > cp -dpfr $(STAGING_DIR)/usr/lib/qt/plugins/accessible
> > $(TARGET_DIR)/usr/lib/qt/plugins>
> > +endef
> > +endif
> > +
> > +define QT5DECLARATIVE_INSTALL_TARGET_LIBS
> > + cp -dpf $(STAGING_DIR)/usr/lib/libQt5Qml*.so.* $(TARGET_DIR)/usr/lib
> >
> > cp -dpfr $(STAGING_DIR)/usr/lib/qt/plugins/qml*
> > $(TARGET_DIR)/usr/lib/qt/plugins>
> > + $(QT5DECLARATIVE_INSTALL_TARGET_QUICK_LIBS)
> >
> > endef
>
> I am still unsure to understand what's the difference between
> qt5declarative and qt5quick exactly. But here, you're installing
> libQt5Qml and the qml plugins as soon as the qt5declarative package is
> enabled, even if the quick module is disabled.
>
> But then, in PATCH 4/6, you only install QML files if the quick module
> is enabled. So I'm a bit confused as to what is needed to actually use
> qml files.
>
> Could you explain a bit more the interaction/difference between
> qt5declarative and the quick module?
qt5quick1 includes the old libs, interpreter, modules, etc. It is probably provided to
ease porting from Qt 4.x. So it has no dependency on qt5declarative.
QML is the name of the language. Quick is the name of QML module kit that is used to
create user interfaces. qt5declarative contains both the interpreter and Quick module
kit. It seems possible to use QML without Quick.
QML files in the other qt5* modules depend on Quick modules. Those are not built
when quick is disabled.
Regards,
Fatih
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140720/3a111504/attachment.html>
next prev parent reply other threads:[~2014-07-20 11:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-19 17:33 [Buildroot] [PATCH 0/6] qt5: dependency fixes Fatih Aşıcı
2014-07-19 17:33 ` [Buildroot] [PATCH 1/6] qt5multimedia: make qt5declarative dependency optional Fatih Aşıcı
2014-07-20 10:02 ` Thomas Petazzoni
2014-07-20 11:20 ` Fatih Aşıcı
2014-07-19 17:33 ` [Buildroot] [PATCH 2/6] qt5base: allow selection of OpenGL API Fatih Aşıcı
2014-07-20 10:02 ` Thomas Petazzoni
2014-07-19 17:33 ` [Buildroot] [PATCH 3/6] qt5declarative: add an option for quick module Fatih Aşıcı
2014-07-20 10:04 ` Thomas Petazzoni
2014-07-20 11:33 ` Fatih Aşıcı [this message]
2014-07-19 17:33 ` [Buildroot] [PATCH 4/6] qt5: install qmls if quick module is selected Fatih Aşıcı
2014-07-19 17:33 ` [Buildroot] [PATCH 5/6] qt5graphicaleffects: depend on quick module Fatih Aşıcı
2014-07-19 17:33 ` [Buildroot] [PATCH 6/6] qt5quickcontrols: " Fatih Aşıcı
2014-07-21 20:00 ` [Buildroot] [PATCH 0/6] qt5: dependency fixes 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=2568185.NtVTRxoxRO@asici \
--to=fatih.asici@gmail.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