From: "André Draszik" <git@andred.net>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH 1/2] asio: DEPENDS on openssl
Date: Wed, 9 Nov 2016 15:55:11 +0000 [thread overview]
Message-ID: <20161109155512.10972-1-git@andred.net> (raw)
From: André Draszik <adraszik@tycoint.com>
asio may or may not build examples and tests that
depend on OpenSSL, alas, it has no way to explicitly
enable or disable OpenSSL support, which is enabled
unconditionally whenever openssl/ssl.h can be found.
Due to that we get non-deterministic build behaviour,
based on whether or not some other package pulled
OpenSSL into the sysroot before asio's configure is
running.
Additionally, we can get random compilation failures
if openssl/ssl.h exists during configure time, but is
removed from sysroot later, e.g. due to a concurrent
rebuild of OpenSSL at the same time as building asio.
Having an explicit DEPENDS avoids both these problems.
We can not use PACKAGECONFIG, because as mentioned
above there is no way to explicitly disable OpenSSL
support.
Signed-off-by: André Draszik <adraszik@tycoint.com>
Reviewed-by: Sylvain Lemieux <slemieux@tycoint.com>
---
meta-oe/recipes-support/asio/asio.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-oe/recipes-support/asio/asio.inc b/meta-oe/recipes-support/asio/asio.inc
index 9cea824..54f78e4 100644
--- a/meta-oe/recipes-support/asio/asio.inc
+++ b/meta-oe/recipes-support/asio/asio.inc
@@ -6,7 +6,7 @@ HOMEPAGE = "http://think-async.com/Asio"
SECTION = "libs"
LICENSE = "BSL-1.0"
-DEPENDS = "boost"
+DEPENDS = "boost openssl"
SRC_URI = "${SOURCEFORGE_MIRROR}/asio/${BP}.tar.bz2"
--
2.10.2
next reply other threads:[~2016-11-09 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 15:55 André Draszik [this message]
2016-11-09 15:55 ` [meta-oe][PATCH 2/2] asio: fix a musl compilation warning André Draszik
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=20161109155512.10972-1-git@andred.net \
--to=git@andred.net \
--cc=openembedded-devel@lists.openembedded.org \
/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