David, Really thanks for your helps on this.
For the include path issue, yes, "....../openssl/crypto/include" may include all symlinked header file. But it may depend on the unpack utility (esp. In Windows). Some unpack tool will ignore those symlink files or replace the content directly in Windows. That's why we need one install script before to make sure all header files were in place. Best Regards & Thanks, LONG, Qin -----Original Message----- From: David Woodhouse [mailto:dw...@infradead.org] Sent: Friday, July 24, 2015 4:49 AM To: Andrew Fish Cc: edk2-devel@lists.sourceforge.net Subject: Re: [edk2] Merging OpenSSL support On Thu, 2015-07-23 at 13:37 -0700, Andrew Fish wrote: > > David, > > What I did for the acpica dump tool is I made a DEC file for the blob > of code from another project and I added the [Includes] section to the > DEC. Then the INF just depends on DEC for the package that represents > the 3rd party. You have to update the DEC if the non edk2 project > changes its include path, but otherwise your good to go. Oh, I don't even need a new DEC file. It's sufficient just to add to the [Includes] section of CryptoPkg/CryptoPkg.dec: --- a/CryptoPkg/CryptoPkg.dec +++ b/CryptoPkg/CryptoPkg.dec @@ -24,6 +24,8 @@ [Includes] Include + Library/OpensslLib/openssl/include + Library/OpensslLib/openssl/crypto/include [LibraryClasses] ## @libraryclass Provides basic library functions for cryptographic primitives. I've pushed that out to my tree now, so there's no need to run Install.sh at all. Thanks again. -- dwmw2 ------------------------------------------------------------------------------ _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
