public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Tiger Liu(BJ-RD)" <tigerliu@zhaoxin.com>
To: gaoliming <gaoliming@byosoft.com.cn>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: 答复: [edk2-devel] OpensslLib compiling error : cannot open include file : openssl/aes.h
Date: Wed, 14 Oct 2020 07:25:38 +0000	[thread overview]
Message-ID: <31d95407a19f43ee97ee02092235d42d@zhaoxin.com> (raw)
In-Reply-To: <003801d6a1eb$d2d15910$78740b30$@byosoft.com.cn>

Hi, liming:
Got it.

Is Cc_resp.txt produced by compiler automatically? Or by UDK build tools?

The problem I met may be caused by violating the limitation length of the compiler command line.
After trim the length, could pass the failed point.

Thanks
-----邮件原件-----
发件人: gaoliming <gaoliming@byosoft.com.cn>
发送时间: 2020年10月14日 13:35
收件人: devel@edk2.groups.io; Tiger Liu(BJ-RD) <TigerLiu@zhaoxin.com>
主题: 回复: [edk2-devel] OpensslLib compiling error : cannot open include file : openssl/aes.h

cc_resp.txt includes the compiler flag and include path. It will be used by the compiler. Then, the compile command line length can be reduced. It can avoid nmake limitation of the command line length 4096.

Thanks
Liming
> -----邮件原件-----
> 发件人: bounce+27952+66197+4905953+8761045@groups.io
> <bounce+27952+66197+4905953+8761045@groups.io> 代表 Tiger
> Liu(BJ-RD)
> 发送时间: 2020年10月14日 9:45
> 收件人: gaoliming <gaoliming@byosoft.com.cn>; devel@edk2.groups.io
> 主题: 答复: [edk2-devel] OpensslLib compiling error : cannot open include
> file : openssl/aes.h
>
> Hi, Liming:
> From Build.log, it seems include path is ok:
> ......
> cl.exe"
> /Foy:\Build\ZxxPlatformPkg\DEBUG_VS2015x86\X64\CryptoPkg\Library\Base
> CryptLib\RuntimeCryptLib\OUTPUT\Hash\ /showIncludes /nologo /c /GS-
> /W4 /Gs32768 /D UNICODE /O1b2s /GL /Gy /FIAutoGen.h /EHs-c- /GR- /GF
> /Z7 /Gw /wd4090  -
> ......
> /Iy:\CryptoPkg  /Iy:\CryptoPkg\Include  /Iy:\CryptoPkg\Private
> /Iy:\CryptoPkg\Library\Include
> /Iy:\CryptoPkg\Library\OpensslLib\openssl\include
> y:\CryptoPkg\Library\BaseCryptLib\Hash\CryptSm3.c
> y:\CryptoPkg\Library\BaseCryptLib\Hash\CryptMd5.c
> y:\CryptoPkg\Library\BaseCryptLib\Hash\CryptSha256.c
> y:\CryptoPkg\Library\BaseCryptLib\Hash\CryptSha512Null.c
> y:\CryptoPkg\Library\BaseCryptLib\Hash\CryptSha1.c
>
> And BaseCryptLib / IntrinsicLib compiled successfully.
>
> And I found a cc_resp.txt file in
> Build\...\DEBUG_VS2015x86\X64\CryptoPkg\Library\OpensslLib\OpensslLib\
> OUTPUT
> Why produce a cc_resp.txt?
>
> Thanks
> -----邮件原件-----
> 发件人: gaoliming <gaoliming@byosoft.com.cn>
> 发送时间: 2020年10月13日 18:03
> 收件人: devel@edk2.groups.io; Tiger Liu(BJ-RD) <TigerLiu@zhaoxin.com>
> 主题: 回复: [edk2-devel] OpensslLib compiling error : cannot open include
> file : openssl/aes.h
>
> Can you print the full build log and check the compiler include path?
>
> Is this a clean build issue or incremental build issue?
>
> Thanks
> Liming
> > -----邮件原件-----
> > 发件人: bounce+27952+66166+4905953+8761045@groups.io
> > <bounce+27952+66166+4905953+8761045@groups.io> 代表 Tiger
> > Liu(BJ-RD)
> > 发送时间: 2020年10月13日 16:38
> > 收件人: devel@edk2.groups.io
> > 主题: [edk2-devel] OpensslLib compiling error : cannot open include file :
> > openssl/aes.h
> >
> > Hi, experts:
> > When I compiled OpensslLib, I met a problem:
> > ......
> > \CryptoPkg\Library\OpensslLib\openssl\crypto\aes\aes_core.c(42):
> > fatal error C1083: Cannot open include file: 'openssl/crypto.h': No
> > such file or directory
> > \CryptoPkg\Library\OpensslLib\openssl\crypto\aes\aes_misc.c(10):
> > fatal error C1083: Cannot open include file: 'openssl/opensslv.h':
> > No such file or directory ......
> >
> > But these files exist in
> > CryptoPkg\Library\OpensslLib\openssl\include\openssl .
> >
> > Does anybody meet same problems?
> >
> > Note:
> > CryptoPkg.dec has also declared this include path:
> > ......
> > [Includes.Common.Private]
> >   Private
> >   Library/Include
> >   Library/OpensslLib/openssl/include
> > ......
> >
> > Thanks
> >
> >
> > 保密声明:
> > 本邮件含有保密或专有信息,仅供指定收件人使用。严禁对本邮件或
> 其
> > 内容做任何未经授权的查阅、使用、复制或转发。
> > CONFIDENTIAL NOTE:
> > This email contains confidential or legally privileged information
> > and is for the sole use of its intended recipient. Any unauthorized
> > review, use, copying or forwarding of this email or the content of
> > this email is
> strictly prohibited.
> >
> >
> >
> >
>
>
>
>
>
> 保密声明:
> 本邮件含有保密或专有信息,仅供指定收件人使用。严禁对本邮件或其
> 内容做任何未经授权的查阅、使用、复制或转发。
> CONFIDENTIAL NOTE:
> This email contains confidential or legally privileged information and
> is for the sole use of its intended recipient. Any unauthorized
> review, use, copying or forwarding of this email or the content of this email is strictly prohibited.
>
>
> 
>





保密声明:
本邮件含有保密或专有信息,仅供指定收件人使用。严禁对本邮件或其内容做任何未经授权的查阅、使用、复制或转发。
CONFIDENTIAL NOTE:
This email contains confidential or legally privileged information and is for the sole use of its intended recipient. Any unauthorized review, use, copying or forwarding of this email or the content of this email is strictly prohibited.

  reply	other threads:[~2020-10-14  7:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13  8:38 [edk2-devel] OpensslLib compiling error : cannot open include file : openssl/aes.h Tiger Liu(BJ-RD)
2020-10-13 10:03 ` 回复: " gaoliming
2020-10-14  1:45   ` 答复: " Tiger Liu(BJ-RD)
2020-10-14  5:35     ` 回复: " gaoliming
2020-10-14  7:25       ` Tiger Liu(BJ-RD) [this message]
2020-10-14 11:55         ` Bob Feng

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-list 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=31d95407a19f43ee97ee02092235d42d@zhaoxin.com \
    --to=devel@edk2.groups.io \
    /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