From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] mutt: Add options for imap/pop3 support, enable optional iconv/OpenSSL support
Date: Sun, 13 Apr 2014 14:00:19 +0200 [thread overview]
Message-ID: <20140413140019.6fce5bf2@skate> (raw)
In-Reply-To: <1397381763-15489-2-git-send-email-bernd.kuhls@t-online.de>
Dear Bernd Kuhls,
On Sun, 13 Apr 2014 11:36:03 +0200, Bernd Kuhls wrote:
> +ifeq ($(BR2_PACKAGE_LIBICONV),y)
> +MUTT_DEPENDENCIES += libiconv
> +MUTT_CONF_OPT += --enable-iconv
> +else
> +MUTT_CONF_OPT += --disable-iconv
> +endif
The libiconv package provides libiconv support for uClibc toolchains
that don't have locale enabled.
But if you're using an uClibc toolchain with locale support enabled, or
a glibc toolchain, then iconv support *is* available, without the
libiconv package enabled. However, with your code, iconv support will
be disabled in mutt in such cases.
Maybe this is an area we need to improve a bit, by providing a Kconfig
option or something like that.
> +# SSL support is only used by imap or pop3 module
> +ifeq ($(findstring xy,x$(BR2_PACKAGE_MUTT_IMAP)$(BR2_PACKAGE_MUTT_POP3)),xy)
This could maybe be:
ifneq ($(BR2_PACKAGET_MUTT_IMAP)$(BR2_PACKAGE_MUTT_POP3),)
> +ifeq ($(BR2_PACKAGE_OPENSSL),y)
> +MUTT_DEPENDENCIES += openssl
> +MUTT_CONF_OPT += --with-ssl=$(STAGING_DIR)/usr
> +else
> +MUTT_CONF_OPT += --without-ssl
> +endif
> +else
> +MUTT_CONF_OPT += --without-ssl
> +endif
> +
> $(eval $(autotools-package))
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-04-13 12:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-13 9:36 [Buildroot] [PATCH 1/2] mutt: Bump version to 1.5.23 Bernd Kuhls
2014-04-13 9:36 ` [Buildroot] [PATCH 2/2] mutt: Add options for imap/pop3 support, enable optional iconv/OpenSSL support Bernd Kuhls
2014-04-13 12:00 ` Thomas Petazzoni [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=20140413140019.6fce5bf2@skate \
--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