From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 5/9] package/libnetconf2: add package
Date: Wed, 9 Oct 2019 14:15:04 +0200 [thread overview]
Message-ID: <20191009141504.37bf7928@windsurf> (raw)
In-Reply-To: <20191009112656.21232-6-heiko.thiery@gmail.com>
Hello Heiko,
On Wed, 9 Oct 2019 13:26:52 +0200
heiko.thiery at gmail.com wrote:
> diff --git a/package/libnetconf2/Config.in b/package/libnetconf2/Config.in
> new file mode 100644
> index 0000000000..986e49fac5
> --- /dev/null
> +++ b/package/libnetconf2/Config.in
> @@ -0,0 +1,37 @@
> +config BR2_PACKAGE_LIBNETCONF2
> + bool "libnetconf2"
> + depends on BR2_TOOLCHAIN_HAS_THREADS
> + depends on !BR2_STATIC_LIBS
> + depends on BR2_USE_MMU
> + select BR2_PACKAGE_LIBYANG
> + select BR2_PACKAGE_LIBSSH
> + select BR2_PACKAGE_LIBSSH_SERVER
I thought libssh was now an optional dependency ?
> + help
> + libnetconf2 is a NETCONF library in C intended for building
> + NETCONF clients and servers.
> +
> + https://github.com/CESNET/libnetconf2
> +
> +config BR2_PACKAGE_LIBNETCONF2_SSH
> + bool
> + help
> + SSH support for libnetconf2
> +
> +config BR2_PACKAGE_LIBNETCONF2_TLS
> + bool
> + help
> + TLS support for libnetconf2
Do we need configurable options for this ? In general, we prefer to
have automatic dependencies, i.e just rely on whether a dependent
package is enabled or not. This would give in your .mk file:
+ifeq ($(BR2_PACKAGE_LIBSSH_SERVER),y)
+LIBNETCONF2_CONF_OPTS += -DENABLE_SSH=ON
+LIBNETCONF2_DEPENDENCIES += libssh
+else
+LIBNETCONF2_CONF_OPTS += -DENABLE_SSH=OFF
+endif
> +config BR2_PACKAGE_HOST_LIBNETCONF2_SSH
> + bool
> + help
> + SSH support for host-libnetconf2
> +
> +config BR2_PACKAGE_HOST_LIBNETCONF2_TLS
> + bool
> + help
> + TLS support for host-libnetconf2
We generally don't make host packages configurable, and if they are,
certainly not with options in Config.in, but in Config.in.host. Do you
really need the host variant of libnetconf2 to have SSL/TLS support ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-10-09 12:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 11:26 [Buildroot] [PATCH v2 0/9] Add netopeer2 package (and dependencies) heiko.thiery at gmail.com
2019-10-09 11:26 ` [Buildroot] [PATCH v2 1/9] package/libev: use host-autotools-package macro heiko.thiery at gmail.com
2019-10-09 11:26 ` [Buildroot] [PATCH v2 2/9] package/libssh: " heiko.thiery at gmail.com
2019-10-09 11:26 ` [Buildroot] [PATCH v2 3/9] package/libavl: add package heiko.thiery at gmail.com
2019-10-09 12:25 ` Thomas Petazzoni
2019-10-09 16:04 ` Michael Walle
2019-10-09 19:27 ` Thomas Petazzoni
2019-10-10 8:20 ` Michael Walle
2019-10-10 8:25 ` Thomas Petazzoni
2019-10-09 11:26 ` [Buildroot] [PATCH v2 4/9] package/libyang: " heiko.thiery at gmail.com
2019-10-09 11:26 ` [Buildroot] [PATCH v2 5/9] package/libnetconf2: " heiko.thiery at gmail.com
2019-10-09 12:15 ` Thomas Petazzoni [this message]
2019-10-09 12:54 ` Heiko Thiery
2019-10-09 12:59 ` Thomas Petazzoni
2019-10-09 11:26 ` [Buildroot] [PATCH v2 6/9] package/sysrepo: " heiko.thiery at gmail.com
2019-10-09 11:26 ` [Buildroot] [PATCH v2 7/9] package/netopeer2-keystored: " heiko.thiery at gmail.com
2019-10-09 12:12 ` Thomas Petazzoni
2019-10-09 13:14 ` Heiko Thiery
2019-10-09 13:34 ` Thomas Petazzoni
2019-10-09 13:43 ` Peter Korsgaard
2019-10-09 15:53 ` Yann E. MORIN
2019-10-09 17:03 ` Heiko Thiery
2019-10-09 17:08 ` Heiko Thiery
2019-10-09 18:15 ` Yann E. MORIN
2019-10-09 19:14 ` Arnout Vandecappelle
2019-10-09 19:45 ` Heiko Thiery
2019-10-09 19:57 ` Heiko Thiery
2019-10-09 11:26 ` [Buildroot] [PATCH v2 8/9] package/netopeer2-server: " heiko.thiery at gmail.com
2019-10-09 11:26 ` [Buildroot] [PATCH v2 9/9] package/netopeer2-cli: " heiko.thiery at gmail.com
2019-10-09 12:30 ` Thomas Petazzoni
2019-10-09 15:57 ` [Buildroot] [PATCH v2 0/9] Add netopeer2 package (and dependencies) Michael Walle
2019-10-23 11:07 ` Heiko Thiery
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=20191009141504.37bf7928@windsurf \
--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 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.