From: Sagaert Johan <sagaert.johan@skynet.be>
To: buildroot@busybox.net
Subject: [Buildroot] Libcurl : to depend or not to depend ?
Date: Wed, 21 Mar 2012 17:50:26 +0100 [thread overview]
Message-ID: <AD9141CB33AC4D019D399FFCCB3E46D3@JohanW7> (raw)
In-Reply-To: <20120321162014.6e2fd485@skate>
Thomas
I know what to do, but in case you need openssl and you also want libcurl BUT without SSL there is no way to build it like it is
now.
The trick i use now to build libcurl without ssl is
disabling openssl
build (libcurl gets build without SSL)
enable openssl
build (libcurl does'nt change and i also have openssl now.)
-----Oorspronkelijk bericht-----
Van: Thomas Petazzoni [mailto:thomas.petazzoni at free-electrons.com]
Verzonden: woensdag 21 maart 2012 16:20
Aan: Sagaert Johan
CC: buildroot at busybox.net
Onderwerp: Re: [Buildroot] Libcurl : to depend or not to depend ?
Hello,
Le Wed, 21 Mar 2012 16:06:52 +0100,
"Sagaert Johan" <sagaert.johan@skynet.be> a ?crit :
> After my issue last week with libcurl it seems that libcurl uses
> openssl if it has been found. (if it was build before libcurl) If its not found then libcurl simply has no SSL support.
> So libcurl is'nt really dependend of openssl.
> It may be better i think to have an option in the config to enable/disable ssl for libcurl.
> In case ssl is enabled then libcurl should be made dependend of openssl.
libcurl already has the following code:
ifeq ($(BR2_PACKAGE_OPENSSL),y)
LIBCURL_DEPENDENCIES += openssl
LIBCURL_CONF_ENV += ac_cv_lib_crypto_CRYPTO_lock=yes # configure adds the cross openssl dir to LD_LIBRARY_PATH which screws up #
native stuff during the rest of configure when target == host.
# Fix it by setting LD_LIBRARY_PATH to something sensible so those libs # are found first.
LIBCURL_CONF_ENV += LD_LIBRARY_PATH=$$LD_LIBRARY_PATH:/lib:/usr/lib
LIBCURL_CONF_OPT += --with-ssl=$(STAGING_DIR)/usr --with-random=/dev/urandom else LIBCURL_CONF_OPT += --without-ssl endif
Which means that:
* If the OpenSSL package is selected, then we guarantee that it is
build *before* libcurl, and libcurl is built with OpenSSL support.
* If the OpenSSL package is not selected, then we force libcurl to be
compiled without SSL support
It doesn't work for you?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-03-21 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 15:06 [Buildroot] Libcurl : to depend or not to depend ? Sagaert Johan
2012-03-21 15:20 ` Thomas Petazzoni
2012-03-21 16:50 ` Sagaert Johan [this message]
2012-03-21 17:05 ` Thomas Petazzoni
2012-03-21 22:00 ` Peter Korsgaard
2012-03-21 22:30 ` Thomas Petazzoni
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=AD9141CB33AC4D019D399FFCCB3E46D3@JohanW7 \
--to=sagaert.johan@skynet.be \
--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