From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/5] qt: define license
Date: Wed, 6 Feb 2013 17:58:33 +0100 [thread overview]
Message-ID: <20130206175833.6c382929@skate> (raw)
In-Reply-To: <1360167853-7177-3-git-send-email-luca@lucaceresoli.net>
Dear Luca Ceresoli,
On Wed, 6 Feb 2013 17:24:11 +0100, Luca Ceresoli wrote:
> +QT_LICENSE = LGPLv2.1 with exceptions or GPLv3 or commercial
> +QT_LICENSE_FILES = LICENSE.LGPL LGPL_EXCEPTION.txt LICENSE.GPL3
If Qt5, I've done:
+ifeq ($(BR2_PACKAGE_QT5BASE_LICENSE_APPROVED),y)
+QT5BASE_CONFIGURE_OPTS += -opensource -confirm-license
+QT5BASE_LICENSE = LGPLv2.1 or GPLv3.0
+QT5BASE_LICENSE_FILES = LICENSE.GPL LICENSE.LGPL LGPL_EXCEPTION.txt
+else
+QT5BASE_LICENSE = Commercial license
+QT5BASE_REDISTRIBUTE = NO
+endif
See
http://git.free-electrons.com/users/thomas-petazzoni/buildroot/commit/?h=qt5&id=7c1f7b9967d814e3f5c838e7090ac04b9d06af51
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-02-06 16:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 16:24 [Buildroot] [PATCH 1/5] ffmpeg: define license Luca Ceresoli
2013-02-06 16:24 ` [Buildroot] [PATCH 2/5] omap-u-boot-utils: " Luca Ceresoli
2013-02-06 16:24 ` [Buildroot] [PATCH 3/5] qt: " Luca Ceresoli
2013-02-06 16:58 ` Thomas Petazzoni [this message]
2013-02-06 20:04 ` Arnout Vandecappelle
2013-02-07 8:34 ` Luca Ceresoli
2013-02-07 17:01 ` Arnout Vandecappelle
2013-02-07 22:40 ` Luca Ceresoli
2013-02-06 16:24 ` [Buildroot] [PATCH 4/5] fbset: " Luca Ceresoli
2013-02-07 20:36 ` Peter Korsgaard
2013-02-06 16:24 ` [Buildroot] [PATCH 5/5] ccache: " Luca Ceresoli
2013-02-06 20:04 ` [Buildroot] [PATCH 1/5] ffmpeg: " Arnout Vandecappelle
2013-02-06 22:13 ` Peter Korsgaard
2013-02-07 8:38 ` Luca Ceresoli
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=20130206175833.6c382929@skate \
--to=thomas.petazzoni@free-electrons.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.