From: Pete Batard <pete@akeo.ie>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Gao, Liming" <liming.gao@intel.com>
Subject: Re: [PATCH v2 2/4] BaseTools: Add VS2017 tool chain in BaseTools tools_def.template
Date: Mon, 20 Nov 2017 18:41:27 +0000 [thread overview]
Message-ID: <8770dd47-c295-c875-7448-46893f1471b4@akeo.ie> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E18099E@SHSMSX104.ccr.corp.intel.com>
Hi Liming,
On 2017.11.20 08:46, Gao, Liming wrote:
> Here, I suggest to mention VS version 15.2 or above, because vswhere.exe depends on this version.
> After later, you may also update this version to 15.4 for ARM and AARCH64 support.
I assume you mean replacing the "Microsoft Visual Studio 2017
Professional or Community Edition" from the comment with something like
"Microsoft Visual Studio 2017 version 15.2 or later", right?
If so, I will do that and submit a v3.
Do you think the possibility of adding vswhere.exe to
BaseTools\Bin\Win32 is also worth exploring? For one thing this would
solve the issue of locating 15.2 VS 2017 (as well as nonstandard
installations that may have removed the installer directory), and the
executable is both Open Source (MIT) and redistributable.
The other possibility of course is to let pre 15.2 VS2017 fail the
detection process, and expect users to get a hint that they need an
updated version from the comments in tools_def...
Regards,
/Pete
next prev parent reply other threads:[~2017-11-20 18:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 13:08 [PATCH v2 0/4] Add VS2017 tool chain for evaluation Pete Batard
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 [this message]
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=8770dd47-c295-c875-7448-46893f1471b4@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