On Fri, 2016-03-11 at 09:00 +0000, David Woodhouse wrote: > On Wed, 2016-02-24 at 16:15 +0800, Jiaxin Wu wrote: > > --- a/CryptoPkg/CryptoPkg.dsc > > +++ b/CryptoPkg/CryptoPkg.dsc > > @@ -48,10 +48,11 @@ > > > > UefiDriverEntryPoint|MdePkg/Library/UefiDriverEntryPoint/UefiDriver > > EntryPoint.inf > > > > UefiApplicationEntryPoint|MdePkg/Library/UefiApplicationEntryPoint/ > > UefiApplicationEntryPoint.inf > > > > IntrinsicLib|CryptoPkg/Library/IntrinsicLib/IntrinsicLib.inf > > OpensslLib|CryptoPkg/Library/OpensslLib/OpensslLib.inf > > + OpensslTlsLib|CryptoPkg/Library/OpensslLib/OpensslTlsLib.inf > > One more thing... does this *need* to be a separate library? > > It looks like the libraries are built into an archive and then linked > statically. So only those objects which are *referenced* are actually > pulled into the build. Which means that if we just *add* the ssl/ > directory to the OpensslLib build, it will only be pulled in if > something *uses* it. Doesn't it?
I package it here: https://build.opensuse.org/package/show/home:jejb1:UEFI/OVMF in edk2-devel I don't *need* to, but it's really useful having a single linkable sour ce for an openssl EFI library rather than having to build it ourselves (as shim currently does) James
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ edk2-devel mailing list [email protected] https://lists.01.org/mailman/listinfo/edk2-devel
