edk build windows #3831
Unanswered
joe-cryptosecurellc
asked this question in
Q&A
Replies: 2 comments
-
Sorry - I forgot to mention that the same build works on Ubuntu 20.04. |
Beta Was this translation helpful? Give feedback.
0 replies
-
For any include path with .Private like this, the build tools create the concept of a library path that is only available for modules within the same package, in this case, CryptoPkg.
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I cannot build with the edk on windows with openssl. My library will not build because it cannot find the openssl headers.
My library is part of the Security Package. My inf file for my library includes CryptoPkg.dec in the [Packages] list and OpensslLib in the [LibraryClasses] list. The CryptoPkg.dec includes the OpensslLib path in the [Includes.Common.Private] list as "Library/OpensslLib/openssl/crypto/include". My edk is a commit branch from Dec 10, 2019, I gor openssl using "git submodule update --init.
My library source files reference openssl headers as "#include <openssl.aes.h>"
Beta Was this translation helpful? Give feedback.
All reactions