From: Liming Gao <liming.gao@intel.com>
To: edk2-devel@lists.01.org
Subject: [Patch 0/4] Add VS2017 tool chain for evaluation
Date: Wed, 18 Oct 2017 18:48:51 +0800 [thread overview]
Message-ID: <1508323735-14344-1-git-send-email-liming.gao@intel.com> (raw)
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, the similar
VS2017x86, VS2017xASL and VS2017x86xASL tool chain will 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 | 122 ++++++++++++++++++++++++++++++++++++
BaseTools/get_vsvars.bat | 8 +++
BaseTools/set_vsprefix_envs.bat | 30 +++++++++
MdePkg/Include/Ia32/ProcessorBind.h | 4 +-
MdePkg/Include/X64/ProcessorBind.h | 4 +-
Nt32Pkg/Sec/SecMain.inf | 2 +
6 files changed, 166 insertions(+), 4 deletions(-)
--
2.8.0.windows.1
next reply other threads:[~2017-10-18 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 10:48 Liming Gao [this message]
2017-10-18 10:48 ` [Patch 1/4] MdePkg: Disable VS warning 4701 & 4703 for VS2017 Liming Gao
2017-10-19 2:26 ` Ni, Ruiyu
2017-10-18 10:48 ` [Patch 2/4] BaseTools: Add VS2017 tool chain in BaseTools tools_def.template Liming Gao
2017-10-18 10:48 ` [Patch 3/4] BaseTools: Update VS batch file to auto detect VS2017 Liming Gao
2017-10-18 10:48 ` [Patch 4/4] Nt32Pkg: Add VS2017 support in SecMain Liming Gao
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=1508323735-14344-1-git-send-email-liming.gao@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