From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 3/4] openDHT: new package
Date: Fri, 22 Apr 2016 23:30:54 +0200 [thread overview]
Message-ID: <20160422233054.4f05c1a6@free-electrons.com> (raw)
In-Reply-To: <1461358628-9352-4-git-send-email-patrick.keroulas@savoirfairelinux.com>
Hello,
Thanks for this contribution.
On Fri, 22 Apr 2016 16:57:07 -0400, Patrick Keroulas wrote:
> A lightweight C++11 Distributed Hash Table implementation originally
> based on https://github.com/jech/dht by Juliusz Chroboczek.
Please add your Signed-off-by here.
Also, the commit title should be in lower-case, to match the package
name:
opendht: new package
> diff --git a/package/opendht/Config.in b/package/opendht/Config.in
> new file mode 100644
> index 0000000..10bfd23
> --- /dev/null
> +++ b/package/opendht/Config.in
> @@ -0,0 +1,21 @@
> +config BR2_PACKAGE_OPENDHT
> + bool "opendht"
> + depends on BR2_USE_WCHAR #gnutls
Space after #
> + depends on BR2_INSTALL_LIBSTDCPP
> + depends on !BR2_STATIC_LIBS
> + depends on BR2_TOOLCHAIN_HAS_THREADS
> + depends on BR2_TOOLCHAIN_HAS_SYNC_4 #msgpack
Ditto.
> + select BR2_PACKAGE_GNUTLS
> + select BR2_PACKAGE_READLINE
> + select BR2_PACKAGE_MSGPACK
> + help
> + OpenDHT is lightweight C++11 Distributed Hash Table implementation.
> +
> + https://github.com/savoirfairelinux/opendht
Indentation for the help text is one tab + 2 spaces.
> +comment "opendht needs a toolchain w/ C++, thread, dynamic library"
> + depends on !BR2_INSTALL_LIBSTDCPP \
> + || !BR2_USE_WCHAR \
> + || !BR2_TOOLCHAIN_HAS_THREADS \
> + || !BR2_TOOLCHAIN_HAS_SYNC_4 \
> + || BR2_STATIC_LIBS
Please indent the follow-up lines with just one tab, and separate the \
with just one space. Also, the BR2_TOOLCHAIN_HAS_SYNC_4 is an
architecture dependency, so it needs to be handled differently.
Finally, you forgot the wchar dependency in the comment.
You want to have something like:
comment "opendht needs a toolchain w/ C++, thread, dynamic library, wchar"
depends on BR2_TOOLCHAIN_HAS_SYNC_4
depends on !BR2_INSTALL_LIBSTDCPP || !BR2_USE_WCHAR || \
!BR2_TOOLCHAIN_HAS_THREADS || BR2_STATIC_LIBS
> diff --git a/package/opendht/opendht.hash b/package/opendht/opendht.hash
> new file mode 100644
> index 0000000..683957c
> --- /dev/null
> +++ b/package/opendht/opendht.hash
> @@ -0,0 +1,2 @@
> +# from local calculation
We normally write:
# Locally calculated
> +sha256 74ce5a5fc449509cf85912120d4243f93a006465e43ff3100c9c4fbd3001dc41 opendht-468331093345e718b5d269a71b3c52a2eea4797e.tar.gz
> diff --git a/package/opendht/opendht.mk b/package/opendht/opendht.mk
> new file mode 100644
> index 0000000..5bab245
> --- /dev/null
> +++ b/package/opendht/opendht.mk
> @@ -0,0 +1,26 @@
> +################################################################################
> +#
> +# opendht
> +#
> +################################################################################
> +
> +OPENDHT_VERSION = 468331093345e718b5d269a71b3c52a2eea4797e
> +OPENDHT_SITE_METHOD = git
> +#OPENDHT_SITE = $(call github,savoirfairelinux,opendht,$(OPENDHT_VERSION))
> +OPENDHT_SITE = https://github.com/savoirfairelinux/opendht.git
Please use the github function call that you commented out, and remove
the _SITE_METHOD variable.
> +OPENDHT_LICENSE = GPLv3, X11
Which license applies to what part?
> +OPENDHT_LICENSE_FILES = COPYING
> +OPENDHT_AUTORECONF = YES
> +OPENDHT_INSTALL_STAGING = YES
> +OPENDHT_INSTALL_TARGET = YES
This last line is not needed, as it is the default.
> +OPENDHT_CONF_OPTS = --disable-static
Don't do this, let Buildroot pass --{enable,disable}-{static,shared}
depending on the configuration.
> +OPENDHT_CONF_ENV = \
> + GNUTLS_CFLAGS="-I$(STAGING_DIR)/usr/include" \
> + GNUTLS_LIBS="-I$(STAGING_DIR)/usr/lib -lgnutls -lnettle -lhogweed"
Why is this needed? The configure.ac is using pkg-config to find the
details about gnutls and other libraries, so there should really be no
need for such environment variables.
> +OPENDHT_DEPENDENCIES = \
> + host-pkgconf \
> + gnutls \
> + readline \
> + msgpack
> +
> +$(eval $(autotools-package))
Could you rework your patch to take into account those comments, and
send an updated version?
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-04-22 21:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 20:57 [Buildroot] [PATCH v1 0/4] Patrick Keroulas
2016-04-22 20:57 ` [Buildroot] [PATCH v1 1/4] libpjsip: add gnutls support and fix various things Patrick Keroulas
2016-04-22 21:21 ` Thomas Petazzoni
2016-05-03 21:08 ` Patrick Keroulas
2016-05-03 21:43 ` Arnout Vandecappelle
2016-05-04 15:22 ` Patrick Keroulas
2016-05-04 19:23 ` Arnout Vandecappelle
2016-04-22 20:57 ` [Buildroot] [PATCH v1 2/4] msgpack: bump to version 1.4.0 Patrick Keroulas
2016-04-22 21:23 ` Thomas Petazzoni
2016-05-02 20:57 ` Patrick Keroulas
2016-04-22 21:52 ` Thomas Petazzoni
2016-04-22 20:57 ` [Buildroot] [PATCH v1 3/4] openDHT: new package Patrick Keroulas
2016-04-22 21:30 ` Thomas Petazzoni [this message]
2016-04-22 20:57 ` [Buildroot] [PATCH v1 4/4] ring-daemon: " Patrick Keroulas
2016-04-22 22:19 ` Thomas Petazzoni
2016-04-25 14:29 ` Jérôme Oufella
2016-04-25 18:18 ` Patrick Keroulas
2016-04-25 19:24 ` Thomas Petazzoni
2016-04-25 21:20 ` Patrick Keroulas
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=20160422233054.4f05c1a6@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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