public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Cheng, Ching JenX" <ching.jenx.cheng@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Cheng, Ching JenX" <ching.jenx.cheng@intel.com>
Subject: Re: [edk2-devel] [PATCH 0/2] *** Add VS2019 Support ***
Date: Wed, 11 Sep 2019 06:25:24 +0000	[thread overview]
Message-ID: <41C441B9D06FFF49AD23ED447CFBE8B160A1A2@BGSMSX105.gar.corp.intel.com> (raw)
In-Reply-To: <15C34D4FF34E9960.28990@groups.io>

From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of
Cheng, Ching JenX
Sent: Wednesday, September 11, 2019 2:08 PM
To: devel@edk2.groups.io
Subject: [edk2-devel] [PATCH 0/2] *** Add VS2019 Support ***

REF: https://bugzilla.tianocore.org/show_bug.cgi?id=2182

In order to support VS2019 on EDK2, the following patches was modified def and batch files

1. Add VS2019 x86/64 definitions on tools_def.template

2. Add VS2019 support on toolsetup batches, and add version check with command vswhere
     Because VS2019 and VS2017 using the same vswhere to get the InstallationPath

Ching JenX Cheng (2):
  Add VS2019 Toolchain def
  Add VS2019 Support on ToolSetup Batches

 BaseTools/Conf/tools_def.template | 134
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++------------
 BaseTools/get_vsvars.bat          |  39
+++++++++++++++++++++++++++++++--------
 BaseTools/set_vsprefix_envs.bat   |  70
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++-----
 BaseTools/toolsetup.bat           |  16 +++++++++++++---
 edksetup.bat                      |   6 ++++--
 5 files changed, 235 insertions(+), 30 deletions(-)

--
2.21.0.windows.1





           reply	other threads:[~2019-09-11  6:25 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <15C34D4FF34E9960.28990@groups.io>]

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=41C441B9D06FFF49AD23ED447CFBE8B160A1A2@BGSMSX105.gar.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