Re: [PATCH 00/24] CryptoPkg/openssl: update openssl submodule to v3.0
PEI has this (OvmfIa32X64Pkg build):No changes in SEC and PEI.[Jiewen] Do you mean the Crypto consumer in PEI has no size difference? Such as
No size change for Tcg2Pei.
The other modules are not there. Seems they are related to firmware
updates. We don't have that on ovmf as we can simply update the
firmware image files on the host machine ...
Is there some target I could use to test-build those modules?
Any hints where I could get them? Given this happens on windows buildsINFO - OpensslLibCrypto.lib(rsa_lib.obj) : error LNK2001: unresolved external[Jiewen] Please add them to https://github.com/tianocore/edk2/tree/master/CryptoPkg/Library/IntrinsicLib
it's probably somewhere in the microsoft standard C library? Is that
available as open source somewhere?
Seems the idea is to have only one openssl copy in the dxe image by(3) Some NOOPT builds are failing due to the size growing ...[Jiewen] Size becomes big challenge...
calling a protocol instead of linking a lib. Makes sense.
Is this documented somewhere? Is there some easy way to use that as
drop-in replacement? Or do we have to change all crypto users to call
the driver instead of linking the lib?