From: Ross Burton <Ross.Burton@arm.com>
To: "mikko.rapeli@linaro.org" <mikko.rapeli@linaro.org>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [docs] [PATCH 1/4] openssl-native.bbclass: add bbclass
Date: Tue, 4 Oct 2022 13:45:28 +0000 [thread overview]
Message-ID: <06BD1A20-33CE-4201-B484-39BACABDBED3@arm.com> (raw)
In-Reply-To: <Yzw1/WhHjPQTCS8W@nuoska>
On 4 Oct 2022, at 14:32, Mikko Rapeli via lists.openembedded.org <mikko.rapeli=linaro.org@lists.openembedded.org> wrote:
>
>>
>> Somewhere I'm guessing openssl has some common init function?
>
> Sadly, there isn't. Not even a common header file. Or at least
> I did not find any. The engines, modules, config files and certs
> are quite different things compared to the plain shared libraries
> which are already found from LD_LIBRARY_PATH.
To be honest, I’m leaning towards saying that these patches should be applied for native/nativesdk builds (not native).
The patches are _fairly_ isolated, being able to say we’re using them is good, and much better than environment variables needing to be set everywhere.
Ross
prev parent reply other threads:[~2022-10-04 13:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 10:10 [PATCH 1/4] openssl-native.bbclass: add bbclass Mikko Rapeli
2022-10-04 11:09 ` [docs] " Richard Purdie
2022-10-04 11:38 ` Mikko Rapeli
2022-10-04 12:19 ` Richard Purdie
2022-10-04 12:54 ` Mikko Rapeli
2022-10-04 13:09 ` Richard Purdie
2022-10-04 13:32 ` Mikko Rapeli
2022-10-04 13:45 ` Ross Burton [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=06BD1A20-33CE-4201-B484-39BACABDBED3@arm.com \
--to=ross.burton@arm.com \
--cc=mikko.rapeli@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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