From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/2] strongswan: new package
Date: Sun, 24 Mar 2013 11:31:07 -0300 [thread overview]
Message-ID: <514F0E2B.6010207@zacarias.com.ar> (raw)
In-Reply-To: <1360854606-13787-1-git-send-email-jezz@sysmic.org>
On 02/14/2013 12:10 PM, J?r?me Pouiller wrote:
> diff --git a/package/strongswan/Config.in b/package/strongswan/Config.in
> new file mode 100644
> index 0000000..24b30ad
> --- /dev/null
> +++ b/package/strongswan/Config.in
> @@ -0,0 +1,105 @@
> +menuconfig BR2_PACKAGE_STRONGSWAN
> + bool "strongswan"
depends on BR2_USE_MMU # fork()
Strongswan uses fork() so it won't build on nommu architectures like
blackfin.
> +if BR2_PACKAGE_STRONGSWAN
> +
> +config BR2_PACKAGE_STRONGSWAN_OPENSSL
> + bool "Enables OpenSSL based crypto backends"
> + select BR2_PACKAGE_OPENSSL
> +
> +config BR2_PACKAGE_STRONGSWAN_GCRYPT
> + bool "Enables libgcrypt based crypto backends"
> + select BR2_PACKAGE_LIBGCRYPT
> +
> +config BR2_PACKAGE_STRONGSWAN_GMP
> + bool "Enable GNU MP (libgmp) based crypto backends"
> + select BR2_PACKAGE_GMP
> + default y
See section 2 of the INSTALL file, one of OPENSSL/GCRYPT/GMP is required
with GMP being the default if nothing is specified.
These three should be folded into a choice so that a user isn't allowed
to N the three of them and cause build breakage.
> +config BR2_PACKAGE_STRONGSWAN_SQL
> + bool "Enable SQL database configuration backend"
> +
> +endif
You need at least one SQL backend (mysql/sqlite) for this to be of any use.
You could probably do something like...
ifeq ($(BR2_PACKAGE_SQLITE),y)
STRONGSWAN_DEPENEDNCIES += sqlite
STRONGSWAN_CONF_OPT += --enable-sql=yes
endef
ifeq ($(BR2_PACKAGE_MYSQL_CLIENT),y)
STRONGSWAN_DEPENDENCIES += mysql_client
STRONGSWAN_CONF_OPT += --enable-sql=yes
endif
> +STRONGSWAN_VERSION = 5.0.1
Bump to 5.0.2 now that it's out?
Other than what i've mentioned it's looking pretty good now.
Care to send another one?
Thanks!
prev parent reply other threads:[~2013-03-24 14:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 17:43 [Buildroot] [PATCH] strongswan: new package Jérôme Pouiller
2013-02-08 18:02 ` Thomas Petazzoni
2013-02-12 11:19 ` Jérôme Pouiller
2013-02-12 11:19 ` [Buildroot] [[PATCH v2]] " Jérôme Pouiller
2013-02-12 11:25 ` Thomas Petazzoni
2013-02-12 17:59 ` Jezz
2013-02-14 13:25 ` [Buildroot] [PATCH v3] " Jérôme Pouiller
2013-02-14 13:39 ` Thomas Petazzoni
2013-02-14 15:10 ` [Buildroot] [PATCH v4 1/2] " Jérôme Pouiller
2013-02-14 15:10 ` [Buildroot] [PATCH v4 2/2] strongswan: fix build without IPv6 support Jérôme Pouiller
2013-03-24 14:31 ` Gustavo Zacarias
2013-05-13 15:15 ` [Buildroot] [PATCH v5] strongswan: new package Jérôme Pouiller
2013-07-31 16:17 ` Thomas Petazzoni
2013-03-24 14:31 ` Gustavo Zacarias [this message]
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=514F0E2B.6010207@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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.