All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/qt5/qt5scxml: install missing QML module
Date: Sat, 3 Mar 2018 20:51:39 +0100	[thread overview]
Message-ID: <20180303205139.3e62b047@gmx.net> (raw)
In-Reply-To: <20180302222423.678df640@windsurf.home>

Hello Thomas,
On Fri, 2 Mar 2018 22:24:23 +0100, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:

> Hello,
> 
> On Thu, 1 Mar 2018 11:50:03 +0100, Peter Seiderer wrote:
> 
> > The dependency on BR2_PACKAGE_QT5DECLARATIVE_QUICK is not needed, the QtScxml
> > module is build/installed even without enabled BR2_PACKAGE_QT5DECLARATIVE_QUICK...  
> 
> But does it make sense to install QML files if the Qt that has been
> built has no way to use them ? Or am I missing something about what
> BR2_PACKAGE_QT5DECLARATIVE_QUICK is ?

No expert for Qml/QtQuick either, but as explained in [1] 'QML is the Language (just like C++)'
and 'QtQuick is a toolkit for QML, allowing to develop graphical interface in QML language
(there are other toolkits for QML, some are graphical like Sailfish Silica or BlackBerry Cascade,
and some are non-graphical like QBS...'

Qscxml is usable from QtQuick, but QtQuick is no prerequisite to use Qscxml (from a theoretical
point of view (and practical the QML module is buildable  without QtQuick))....

Regards,
Peter

[1] https://stackoverflow.com/questions/19696153/difference-between-qt-qml-and-qt-quick

> 
> Best regards,
> 
> Thomas

  reply	other threads:[~2018-03-03 19:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-01  7:46 [Buildroot] [PATCH] package/qt5/qt5scxml: install missing QML module Bartosz Bilas
2018-03-01 10:50 ` Peter Seiderer
2018-03-01 12:26   ` Bartosz Biłas
2018-03-01 13:52     ` Peter Seiderer
2018-03-02 21:24   ` Thomas Petazzoni
2018-03-03 19:51     ` Peter Seiderer [this message]
2018-03-07 14:08     ` Bartosz Biłas

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=20180303205139.3e62b047@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.