From: Julien CORJON <corjon.j@ecagroup.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] qt5quickcontrols2: new package
Date: Mon, 18 Apr 2016 11:21:19 +0000 [thread overview]
Message-ID: <5714C32E.4080907@ecagroup.com> (raw)
In-Reply-To: <570AB8F9.5060408@mind.be>
Arnout, all,
Le 10/04/2016 22:35, Arnout Vandecappelle a ?crit :
> On 04/08/16 23:33, Peter Seiderer wrote:
>> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
>
> Tested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
>
> However...
>
>> ---
>> Changes v1 -> v2:
>> - move menu entry to 'technology preview' section
>> - add QT5_GL_AVAILABLE/QT5_JSCORE_AVAILABLE dependency comment
>> - install the right qt5quickcontrols2 files to target
>> (all suggested by Julien Corjon)
... snip ...
>> +ifeq ($(BR2_PACKAGE_QT5BASE_LICENSE_APPROVED),y)
>> +QT5QUICKCONTROLS2_LICENSE = GPLv3 or LGPLv3, GFDLv1.3 (docs)
>
> The source files specify GPLv2+ or LGPLv3
QtQuickControls2 is a tech-preview package and follow the upcoming Qt
license convention[1]. That's why this module only have GPLv3 or LGPLv3
license possibility (but i did not go with fossology to check).
Regards,
Julien
[1] http://blog.qt.io/blog/2016/03/16/qt-5-6-released/
>
>
> Regards,
> Arnout
>
>
>> +QT5QUICKCONTROLS2_LICENSE_FILES = LICENSE.GPLv3 LICENSE.LGPLv3
>> LICENSE.FDL
>> +else
>> +QT5QUICKCONTROLS2_LICENSE = Commercial license
>> +QT5QUICKCONTROLS2_REDISTRIBUTE = NO
>> +endif
>> +
>> +define QT5QUICKCONTROLS2_CONFIGURE_CMDS
>> + (cd $(@D); $(TARGET_MAKE_ENV) $(HOST_DIR)/usr/bin/qmake)
>> +endef
>> +
>> +define QT5QUICKCONTROLS2_BUILD_CMDS
>> + $(TARGET_MAKE_ENV) $(MAKE) -C $(@D)
>> +endef
>> +
>> +define QT5QUICKCONTROLS2_INSTALL_STAGING_CMDS
>> + $(TARGET_MAKE_ENV) $(MAKE) -C $(@D) install
>> +endef
>> +
>> +define QT5QUICKCONTROLS2_INSTALL_TARGET_CMDS
>> + cp -dpf $(STAGING_DIR)/usr/lib/libQt5LabsTemplates.so.*
>> $(TARGET_DIR)/usr/lib
>> + cp -dpfr $(STAGING_DIR)/usr/qml/Qt/labs/controls
>> $(TARGET_DIR)/usr/qml/Qt/labs
>> + cp -dpfr $(STAGING_DIR)/usr/qml/Qt/labs/calendar
>> $(TARGET_DIR)/usr/qml/Qt/labs
>> + cp -dpfr $(STAGING_DIR)/usr/qml/Qt/labs/templates
>> $(TARGET_DIR)/usr/qml/Qt/labs
>> +endef
>> +
>> +$(eval $(generic-package))
>>
>
>
next prev parent reply other threads:[~2016-04-18 11:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 21:33 [Buildroot] [PATCH v2] qt5quickcontrols2: new package Peter Seiderer
2016-04-10 20:35 ` Arnout Vandecappelle
2016-04-18 11:21 ` Julien CORJON [this message]
2016-04-18 20:34 ` Thomas Petazzoni
2016-04-18 12:03 ` Julien CORJON
2016-04-18 20:33 ` 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=5714C32E.4080907@ecagroup.com \
--to=corjon.j@ecagroup.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 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.