From: "Stefano Babic" <sbabic@denx.de>
To: zhengruoqin <zhengrq.fnst@cn.fujitsu.com>, yocto@yoctoproject.org
Cc: swupdate <swupdate@googlegroups.com>
Subject: Re: [yocto] [PATCH] [meta-swupdate] Fix build error of dependence.
Date: Thu, 4 Jun 2020 09:22:00 +0200 [thread overview]
Message-ID: <b4d88124-4292-d5f2-8275-3c450551844e@denx.de> (raw)
In-Reply-To: <1591273565-20422-1-git-send-email-zhengrq.fnst@cn.fujitsu.com>
Hi Zheng,
there is a ML for SWUpdate and meta-swupdate (see CC), we are
cross-posting here:
On 04.06.20 14:26, zhengruoqin wrote:
> -c -o mongoose/mongoose.o mongoose/mongoose.c
> | mongoose/mongoose.c:4496:10: fatal error: openssl/ssl.h: No such file
> or directory
>
> Signed-off-by: Zheng Ruoqing <zhengrq.fnst@cn.fujitsu.com>
> ---
> recipes-support/swupdate/swupdate.inc | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/recipes-support/swupdate/swupdate.inc b/recipes-support/swupdate/swupdate.inc
> index 9ea0a8a..3d9a3fa 100644
> --- a/recipes-support/swupdate/swupdate.inc
> +++ b/recipes-support/swupdate/swupdate.inc
> @@ -123,6 +123,9 @@ python () {
> elif 'CONFIG_SSL_IMPL_MBEDTLS=y\n' in features:
> depends += ' mbedtls'
>
> + if 'CONFIG_MONGOOSESSL=y\n' in features:
> + depends += ' openssl'
> +
openSSL is not the only supported SSL library, the Webserver runs also
with mbedTLS. This patch forces to use openSSL and conflicts in case
mbedTLS is used as signing and crypto library.
> if 'CONFIG_JSON=y\n' in features:
> depends += ' json-c'
>
>
>
>
>
Best regards,
Stefano Babic
next prev parent reply other threads:[~2020-06-04 7:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 12:26 [PATCH] [meta-swupdate] Fix build error of dependence zhengruoqin
2020-06-04 7:22 ` Stefano Babic [this message]
2020-06-08 8:49 ` [yocto] " zhengruoqin
2020-06-08 8:55 ` [swupdate] " Stefano Babic
2020-06-18 7:08 ` zhengruoqin
2020-06-18 7:42 ` Stefano Babic
[not found] ` <CAAxSGfY9uDN708Cy5LFd3cgeRMgfBT85o8Pw=mFwL-T66oOe+w@mail.gmail.com>
2020-06-18 8:22 ` Stefano Babic
2020-06-19 6:20 ` zhengruoqin
2020-06-19 8:53 ` Stefano Babic
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=b4d88124-4292-d5f2-8275-3c450551844e@denx.de \
--to=sbabic@denx.de \
--cc=swupdate@googlegroups.com \
--cc=yocto@yoctoproject.org \
--cc=zhengrq.fnst@cn.fujitsu.com \
/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.