All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 6/9] package/sysrepo: add package
Date: Wed, 23 Oct 2019 18:39:42 +0200	[thread overview]
Message-ID: <5e8d93e92af7e12da2c1bdecb3d75f11@walle.cc> (raw)
In-Reply-To: <20191011124131.28246-7-heiko.thiery@gmail.com>

Am 2019-10-11 14:40, schrieb heiko.thiery at gmail.com:
> From: Heiko Thiery <heiko.thiery@kontron.com>
> 
> sysrepo is a YANG-based configuration and operational state
> data store for Unix/Linux applications. It is a dependency
> of Netopeer, a NETCONF server.
> 
> Signed-off-by: Heiko Thiery <heiko.thiery@kontron.com>
> --- /dev/null
> +++ b/package/sysrepo/Config.in
> @@ -0,0 +1,26 @@
> +config BR2_PACKAGE_SYSREPO
> +	bool "sysrepo"
> +	depends on BR2_USE_MMU # libnetconf2
> +	depends on !BR2_STATIC_LIBS
> +	depends on BR2_INSTALL_LIBSTDCPP
> +	depends on BR2_TOOLCHAIN_HAS_THREADS
> +	depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86" # 
> host-protbuf
> +	depends on BR2_HOST_GCC_AT_LEAST_4_8 # host-protobuf
> +	select BR2_PACKAGE_LIBEV
> +	select BR2_PACKAGE_LIBNETCONF2
> +	select BR2_PACKAGE_LIBAVL
> +	select BR2_PACKAGE_LIBYANG
> +	select BR2_PACKAGE_PROTOBUF_C
> +	select BR2_PACKAGE_PCRE
> +	select BR2_PACKAGE_PCRE_UCP
> +	help
> +	  Sysrepo is an YANG-based configuration and operational state
> +	  data store for Unix/Linux applications.
> +
> +	  https://github.com/sysrepo
> +
> +comment "sysrepo needs a toolchain w/ C++, threads, dynamic libraray,
> host gcc >= 4.8"
> +	depends on BR2_USE_MMU
> +	depends on BR2_STATIC_LIBS || !BR2_INSTALL_LIBSTDCPP \
> +		|| !BR2_TOOLCHAIN_HAS_THREADS || !BR2_HOST_GCC_AT_LEAST_4_8
> +	depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86"

Sysrepo comes with examples ([1]), IMHO it would be useful to have a 
switch in Kconfig to automatically build and install these examples.

-michael

[1] 
https://github.com/sysrepo/sysrepo/blob/906927b4ee2dd0d5bd669d193fc851d14919fbd1/CMakeLists.txt#L267

  reply	other threads:[~2019-10-23 16:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11 12:40 [Buildroot] [PATCH v3 0/9] Add netopeer2 package (and dependencies) heiko.thiery at gmail.com
2019-10-11 12:40 ` [Buildroot] [PATCH v3 1/9] package/libev: use host-autotools-package macro heiko.thiery at gmail.com
2019-10-11 12:40 ` [Buildroot] [PATCH v3 2/9] package/libssh: " heiko.thiery at gmail.com
2019-10-11 12:40 ` [Buildroot] [PATCH v3 3/9] package/libavl: add package heiko.thiery at gmail.com
2019-10-22 21:28   ` Thomas Petazzoni
2019-10-11 12:40 ` [Buildroot] [PATCH v3 4/9] package/libyang: " heiko.thiery at gmail.com
2019-10-22 21:30   ` Thomas Petazzoni
2019-10-11 12:40 ` [Buildroot] [PATCH v3 5/9] package/libnetconf2: " heiko.thiery at gmail.com
2019-10-22 21:33   ` Thomas Petazzoni
2019-10-11 12:40 ` [Buildroot] [PATCH v3 6/9] package/sysrepo: " heiko.thiery at gmail.com
2019-10-23 16:39   ` Michael Walle [this message]
2019-10-23 16:43     ` Heiko Thiery
2019-10-11 12:40 ` [Buildroot] [PATCH v3 7/9] package/netopeer2-keystored: " heiko.thiery at gmail.com
2019-10-11 12:40 ` [Buildroot] [PATCH v3 8/9] package/netopeer2-server: " heiko.thiery at gmail.com
2019-10-11 12:40 ` [Buildroot] [PATCH v3 9/9] package/netopeer2-cli: " heiko.thiery at gmail.com

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=5e8d93e92af7e12da2c1bdecb3d75f11@walle.cc \
    --to=michael@walle.cc \
    --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.