From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/9] package/libyang: add package
Date: Wed, 2 Oct 2019 09:25:15 +0200 [thread overview]
Message-ID: <20191002092515.346cc314@windsurf.home> (raw)
In-Reply-To: <20191001143023.698-4-heiko.thiery@gmail.com>
Hello Heiko,
On Tue, 1 Oct 2019 16:30:17 +0200
heiko.thiery at gmail.com wrote:
> diff --git a/package/Config.in b/package/Config.in
> index abea9e2428..04cd466eba 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -1640,6 +1640,7 @@ menu "Networking"
> source "package/libvncserver/Config.in"
> source "package/libwebsock/Config.in"
> source "package/libwebsockets/Config.in"
> + source "package/libyang/Config.in"
> source "package/lksctp-tools/Config.in"
> source "package/mongoose/Config.in"
> source "package/nanomsg/Config.in"
> diff --git a/package/libyang/Config.in b/package/libyang/Config.in
> new file mode 100644
> index 0000000000..cfd2862c15
> --- /dev/null
> +++ b/package/libyang/Config.in
> @@ -0,0 +1,7 @@
> +config BR2_PACKAGE_LIBYANG
> + bool "libyang - YANG data modeling language parser and toolkit"
Should be just:
bool "libyang"
> + depends on !BR2_STATIC_LIBS
> + select BR2_PACKAGE_PCRE
The home page at https://github.com/CESNET/libyang says:
note, that PCRE is supposed to be compiled with unicode support
(configure's options --enable-utf and --enable-unicode-properties)
So I think you need:
select BR2_PACKAGE_PCRE_UTF
Could you make sure it is indeed needed?
> + help
> + Libyang is YANG data modeling language parser and toolkit
> + written (and providing API) in C.
Upstream URL of the project.
Also, you need a Config.in comment like this:
comment "libyang needs a toolchain w/ dynamic library"
depends on BR2_STATIC_LIBS
> diff --git a/package/libyang/libyang.mk b/package/libyang/libyang.mk
> new file mode 100644
> index 0000000000..9005683053
> --- /dev/null
> +++ b/package/libyang/libyang.mk
> @@ -0,0 +1,21 @@
> +################################################################################
> +#
> +# libyang
> +#
> +################################################################################
> +
> +LIBYANG_VERSION = v1.0-r3
> +LIBYANG_SITE = $(call github,CESNET,libyang,$(LIBYANG_VERSION))
> +LIBYANG_LICENSE = BSD-3-Clause
> +LIBYANG_LICENSE_FILES = LICENSE
> +LIBYANG_INSTALL_STAGING = YES
> +LIBYANG_SUPPORTS_IN_SOURCE_BUILD = NO
> +LIBYANG_DEPENDENCIES += pcre
Just =
> +HOST_LIBYANG_DEPENDENCIES += host-pcre
Just =
> +
> +LIBYANG_CONF_OPTS += \
Just =
> + -DENABLE_VALGRIND_TESTS=OFF \
> + -DGEN_PYTHON_BINDINGS=OFF
What about passing the same options to the host variant ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-10-02 7:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 14:30 [Buildroot] [PATCH 1/9] package/libev: use host-autotools-package macro heiko.thiery at gmail.com
2019-10-01 14:30 ` [Buildroot] [PATCH 2/9] package/libssh: " heiko.thiery at gmail.com
2019-10-01 14:30 ` [Buildroot] [PATCH 3/9] package/libredblack: add package heiko.thiery at gmail.com
2019-10-02 7:20 ` Thomas Petazzoni
2019-10-04 8:49 ` Heiko Thiery
2019-10-01 14:30 ` [Buildroot] [PATCH 4/9] package/libyang: " heiko.thiery at gmail.com
2019-10-02 7:25 ` Thomas Petazzoni [this message]
2019-10-04 8:49 ` Heiko Thiery
2019-10-01 14:30 ` [Buildroot] [PATCH 5/9] package/libnetconf2: " heiko.thiery at gmail.com
2019-10-02 7:28 ` Thomas Petazzoni
2019-10-04 8:51 ` Heiko Thiery
2019-10-04 9:07 ` Thomas Petazzoni
2019-10-01 14:30 ` [Buildroot] [PATCH 6/9] package/sysrepo: " heiko.thiery at gmail.com
2019-10-02 9:34 ` Thomas Petazzoni
2019-10-04 8:52 ` Heiko Thiery
2019-10-01 14:30 ` [Buildroot] [PATCH 7/9] package/netopeer2server: " heiko.thiery at gmail.com
2019-10-01 14:30 ` [Buildroot] [PATCH 8/9] package/netopeer2cli: " heiko.thiery at gmail.com
2019-10-01 14:30 ` [Buildroot] [PATCH 9/9] package/netopeer2keystored: " 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=20191002092515.346cc314@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