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 v2 0/2] *** Add VS2019 Support ***
Date: Tue, 17 Sep 2019 03:22:30 +0000	[thread overview]
Message-ID: <41C441B9D06FFF49AD23ED447CFBE8B160A9CB@BGSMSX105.gar.corp.intel.com> (raw)
In-Reply-To: <15C51B795F616549.24469@groups.io>

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

v2: In 01/02, add ARM/AARCH64/EBC Definitions, Combine VS2017_HOST and VS2019_HOST to VS_HOST

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

 BaseTools/Conf/tools_def.template | 220 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------------
 BaseTools/get_vsvars.bat          |  37 ++++++++++++++++++++++++++++++-------
 BaseTools/set_vsprefix_envs.bat   |  70 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-----
 BaseTools/toolsetup.bat           |  16 +++++++++++++---
 edksetup.bat                      |   6 ++++--
 5 files changed, 313 insertions(+), 36 deletions(-)

--
2.21.0.windows.1





       reply	other threads:[~2019-09-17  3:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <15C51B795F616549.24469@groups.io>
2019-09-17  3:22 ` Cheng, Ching JenX [this message]
2019-09-17 14:56   ` [edk2-devel] [PATCH v2 0/2] *** Add VS2019 Support *** Liming Gao
2019-09-18  1:51     ` Cheng, Ching JenX
2019-09-18  8:13       ` 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=41C441B9D06FFF49AD23ED447CFBE8B160A9CB@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