From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/5] Add KF5 package networkmanager-qt
Date: Sun, 1 Jul 2018 00:12:53 +0200 [thread overview]
Message-ID: <20180701001253.38a198e4@windsurf.home> (raw)
In-Reply-To: <20180215204815.14707-3-pinaraf@pinaraf.info>
Hello Pierre,
On Thu, 15 Feb 2018 21:48:13 +0100, Pierre Ducroquet wrote:
> networkmanager-qt is a simple Qt wrapper on the NetworkManager API.
>
> Signed-off-by: Pierre Ducroquet <pinaraf@pinaraf.info>
I've applied this package, after doing a number of changes.
First, I fixed the commit title to follow our convention.
> diff --git a/package/kf5/kf5-networkmanager-qt/Config.in b/package/kf5/kf5-networkmanager-qt/Config.in
> new file mode 100644
> index 0000000000..aff4f39ae2
> --- /dev/null
> +++ b/package/kf5/kf5-networkmanager-qt/Config.in
> @@ -0,0 +1,13 @@
> +config BR2_PACKAGE_KF5_NETWORKMANAGER_QT
> + bool "kf5-networkmanager-qt"
> + select BR2_PACKAGE_KF5_EXTRA_CMAKE_MODULES
> + select BR2_PACKAGE_NETWORK_MANAGER
When you select a package you *must* replicate its dependencies. Since
network-manager has tons of dependencies, and it's pretty obvious for
the user of kf5-networkmanager-qt that network-manager should be
enabled, I've changed from a "select" to a "depends on
BR2_PACKAGE_NETWORK_MANAGER", which avoids the need for replicating the
dependencies.
In addition, you forgot to select BR2_PACKAGE_QT5DBUS. Without this,
the build fails because kf5-networkmanager-qt uses the DBus support in
Qt. This required propagating a few dependencies.
See the final commit for the details.
> index 0000000000..d3c0f96d46
> --- /dev/null
> +++ b/package/kf5/kf5-networkmanager-qt/kf5-networkmanager-qt.hash
> @@ -0,0 +1,2 @@
> +# Locally calculated
> +sha256 0cbbcaa2db1f9bd5445b9c7c5f1e79313df5060f7c31617d673d00f19600755e networkmanager-qt-5.43.0.tar.xz
Updated to 5.47 + hash for license file added.
> +KF5_NETWORKMANAGER_QT_DEPENDENCIES = kf5-extra-cmake-modules network-manager
You were missing qt5base here. Without this, you have no guarantee that
qt5base gets built before, obviously causing a build failure.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-06-30 22:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 20:48 [Buildroot] [PATCH 1/5] Introduce KDE Frameworks 5 packages Pierre Ducroquet
2018-02-15 20:48 ` [Buildroot] [PATCH 2/5] Add first KF5 package : extra-cmake-modules Pierre Ducroquet
2018-06-30 22:10 ` Thomas Petazzoni
2018-02-15 20:48 ` [Buildroot] [PATCH 3/5] Add KF5 package networkmanager-qt Pierre Ducroquet
2018-06-30 22:12 ` Thomas Petazzoni [this message]
2018-02-15 20:48 ` [Buildroot] [PATCH 4/5] Add KF5 package modemmanager-qt Pierre Ducroquet
2018-07-02 21:30 ` Thomas Petazzoni
2018-02-15 20:48 ` [Buildroot] [PATCH 5/5] Add KF5 package kcoreaddons Pierre Ducroquet
2018-06-30 22:08 ` [Buildroot] [PATCH 1/5] Introduce KDE Frameworks 5 packages 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=20180701001253.38a198e4@windsurf.home \
--to=thomas.petazzoni@bootlin.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