From: Pete Batard <pete@akeo.ie>
To: edk2-devel@lists.01.org
Cc: liming.gao@intel.com
Subject: [PATCH v2 0/4] Add VS2017 tool chain for evaluation
Date: Fri, 17 Nov 2017 13:08:33 +0000 [thread overview]
Message-ID: <20171117130837.9164-1-pete@akeo.ie> (raw)
This is an updated version of the proposal sent on 2017-10-18 with
alterations that should facilitate the introduction of ARM and ARM64
support.
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
next reply other threads:[~2017-11-17 13:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 13:08 Pete Batard [this message]
2017-11-17 13:08 ` [PATCH v2 1/4] MdePkg: Disable VS warning 4701 & 4703 for VS2017 Pete Batard
2017-11-17 13:08 ` [PATCH v2 2/4] BaseTools: Add VS2017 tool chain in BaseTools tools_def.template Pete Batard
2017-11-20 8:46 ` Gao, Liming
2017-11-20 18:41 ` Pete Batard
2017-11-22 15:11 ` Gao, Liming
2017-11-17 13:08 ` [PATCH v2 3/4] BaseTools: Update VS batch file to auto detect VS2017 Pete Batard
2017-11-17 13:08 ` [PATCH v2 4/4] Nt32Pkg: Add VS2017 support in SecMain Pete Batard
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=20171117130837.9164-1-pete@akeo.ie \
--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