From: "Zhu, Yonghong" <yonghong.zhu@intel.com>
To: Pete Batard <pete@akeo.ie>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Gao, Liming" <liming.gao@intel.com>,
"Zhu, Yonghong" <yonghong.zhu@intel.com>
Subject: Re: [PATCH v3 0/4] Add VS2017 tool chain for evaluation
Date: Tue, 28 Nov 2017 01:56:22 +0000 [thread overview]
Message-ID: <B9726D6DCCFB8B4CA276A9169B02216D51F3DBAE@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <20171122162610.4748-1-pete@akeo.ie>
Reviewed-by: Yonghong Zhu <yonghong.zhu@intel.com>
Best Regards,
Zhu Yonghong
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Pete Batard
Sent: Thursday, November 23, 2017 12:26 AM
To: edk2-devel@lists.01.org
Cc: Gao, Liming <liming.gao@intel.com>
Subject: [edk2] [PATCH v3 0/4] Add VS2017 tool chain for evaluation
This is a re-send of v2, with a small comment update to indicate that
VS2017 v15.2 or later is required, due to the vswhere.exe requirement.
This patch serial adds VS2017 tool chain in BaseTools tools_def.template.
It enables /WHOLEARCHIVE option to detect the potential code issue.
It can be used to build source code with Visual Studio 2017 on 32bit or 64bit Windows OS. After this tool chain is evaluated, ASL, ARM and ARM64 support can be provided.
And, to avoid more duplicated informations be introduced, the proposal to simplify tools_def.template will be provided.
Liming Gao (4):
MdePkg: Disable VS warning 4701 & 4703 for VS2017
BaseTools: Add VS2017 tool chain in BaseTools tools_def.template
BaseTools: Update VS batch file to auto detect VS2017
Nt32Pkg: Add VS2017 support in SecMain
BaseTools/Conf/tools_def.template | 126 ++++++++++++++++++++
BaseTools/get_vsvars.bat | 8 ++
BaseTools/set_vsprefix_envs.bat | 33 ++++-
MdePkg/Include/Ia32/ProcessorBind.h | 4 +-
MdePkg/Include/X64/ProcessorBind.h | 4 +-
Nt32Pkg/Sec/SecMain.inf | 2 +
6 files changed, 172 insertions(+), 5 deletions(-)
--
2.9.3.windows.2
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2017-11-28 1:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 16:26 [PATCH v3 0/4] Add VS2017 tool chain for evaluation Pete Batard
2017-11-22 16:26 ` [PATCH v3 1/4] MdePkg: Disable VS warning 4701 & 4703 for VS2017 Pete Batard
2017-11-22 16:26 ` [PATCH v3 2/4] BaseTools: Add VS2017 tool chain in BaseTools tools_def.template Pete Batard
2017-11-22 16:26 ` [PATCH v3 3/4] BaseTools: Update VS batch file to auto detect VS2017 Pete Batard
2017-11-22 16:26 ` [PATCH v3 4/4] Nt32Pkg: Add VS2017 support in SecMain Pete Batard
2017-11-28 1:56 ` Zhu, Yonghong [this message]
2017-11-29 8:04 ` [PATCH v3 0/4] Add VS2017 tool chain for evaluation Gao, Liming
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=B9726D6DCCFB8B4CA276A9169B02216D51F3DBAE@SHSMSX103.ccr.corp.intel.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