From: Andreas Naumann <dev@andin.de>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Andreas Naumann <anaumann@ultratronik.de>
Cc: Jesse Van Gavere <jesseevg@gmail.com>,
Samuel Martin <s.martin49@gmail.com>,
Roy Kollen Svendsen <roykollensvendsen@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/qt6/qt6opcua: new package
Date: Mon, 22 Jul 2024 10:12:18 +0200 [thread overview]
Message-ID: <788e9bf3-15bd-4650-809a-9f67a650aeff@andin.de> (raw)
In-Reply-To: <20240717225938.31659b3d@windsurf>
Hi Thomas,
On 17.07.24 22:59, Thomas Petazzoni via buildroot wrote:
> Hello Andreas,
...
>
> Thanks applied, with minor changes, see below.
Thanks for applying and fixing.
>
>> ---
>> package/qt6/Config.in | 1 +
>> package/qt6/qt6opcua/Config.in | 14 +++++++++
>> package/qt6/qt6opcua/qt6opcua.hash | 9 ++++++
>> package/qt6/qt6opcua/qt6opcua.mk | 46 ++++++++++++++++++++++++++++++
>> 4 files changed, 70 insertions(+)
>
> Entry in DEVELOPERS file missing.
ok.
>
>
>
>> create mode 100644 package/qt6/qt6opcua/Config.in
>> create mode 100644 package/qt6/qt6opcua/qt6opcua.hash
>> create mode 100644 package/qt6/qt6opcua/qt6opcua.mk
>>
>> diff --git a/package/qt6/Config.in b/package/qt6/Config.in
>> index e84806d5e4..29c1c25c7f 100644
>> --- a/package/qt6/Config.in
>> +++ b/package/qt6/Config.in
>> @@ -48,6 +48,7 @@ source "package/qt6/qt6core5compat/Config.in"
>> source "package/qt6/qt6declarative/Config.in"
>> source "package/qt6/qt6languageserver/Config.in"
>> source "package/qt6/qt6mqtt/Config.in"
>> +source "package/qt6/qt6opcua/Config.in"
>> source "package/qt6/qt6serialbus/Config.in"
>> source "package/qt6/qt6serialport/Config.in"
>> source "package/qt6/qt6shadertools/Config.in"
>> diff --git a/package/qt6/qt6opcua/Config.in b/package/qt6/qt6opcua/Config.in
>> new file mode 100644
>> index 0000000000..84a51f544f
>> --- /dev/null
>> +++ b/package/qt6/qt6opcua/Config.in
>> @@ -0,0 +1,14 @@
>> +config BR2_PACKAGE_QT6OPCUA
>> + bool "qt6opcua"
>> + select BR2_PACKAGE_QT6BASE_NETWORK
>> + # qt6opcuda needs host-qt6opcua, and host-qt6opcua needs
>> + # network support in qt6base.
>
> Dang, I realize now the indentation here is with spaces, it should have
> been with tabs. I'll fix that up.
Damn, i was using some copypasta and was relying on check-package to
complain.
>
>
>> +QT6OPCUA_LICENSE = \
>> + GPL-2.0 or GPL-3.0 or LGPL-3.0, \
>> + GPL-3.0 WITH Qt-GPL-exception-1.0 (tools), \
>
> The tools are also under "GPL-2.0 or GPL-3.0 or LGPL-3.0" as far I can
> see, so I dropped this line.
Thanks for checking. And was not very confident in how to reliably get
this information. Basically I tried to reflect the contents of
licenseRule.json.
regards,
Andreas
>
> Thanks!
>
> Thomas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-07-22 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 19:48 [Buildroot] [PATCH 1/1] package/qt6/qt6opcua: new package Andreas Naumann
2024-07-17 20:59 ` Thomas Petazzoni via buildroot
2024-07-22 8:12 ` Andreas Naumann [this message]
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=788e9bf3-15bd-4650-809a-9f67a650aeff@andin.de \
--to=dev@andin.de \
--cc=anaumann@ultratronik.de \
--cc=buildroot@buildroot.org \
--cc=jesseevg@gmail.com \
--cc=roykollensvendsen@gmail.com \
--cc=s.martin49@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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