From: "Gao, Liming" <liming.gao@intel.com>
To: "Zhu, Yonghong" <yonghong.zhu@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [Patch 0/3] BaseTools: Replace hardcoding VS path in tools_def.template
Date: Tue, 1 Nov 2016 02:51:52 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14B49C7FA@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1477629824-36252-1-git-send-email-yonghong.zhu@intel.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Yonghong Zhu
Sent: Friday, October 28, 2016 12:44 PM
To: edk2-devel@lists.01.org
Subject: [edk2] [Patch 0/3] BaseTools: Replace hardcoding VS path in tools_def.template
This series patches replace the hardcode VS path in the tools_def.template
file.
Yonghong Zhu (3):
BaseTools: Add a new bat file to set PREFIX envs
BaseTools: Update toolsetup.bat to call the set_vsprefix_envs.bat
BaseTools:introduce PREFIX env for VS tool path
BaseTools/Conf/tools_def.template | 90 +++++++++++++++++----------------
BaseTools/set_vsprefix_envs.bat | 101 ++++++++++++++++++++++++++++++++++++++
BaseTools/toolsetup.bat | 8 +++
3 files changed, 153 insertions(+), 46 deletions(-)
create mode 100644 BaseTools/set_vsprefix_envs.bat
--
2.6.1.windows.1
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2016-11-01 2:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 4:43 [Patch 0/3] BaseTools: Replace hardcoding VS path in tools_def.template Yonghong Zhu
2016-10-28 4:43 ` [Patch 1/3] BaseTools: Add a new bat file to set PREFIX envs Yonghong Zhu
2016-10-28 4:43 ` [Patch 2/3] BaseTools: Update toolsetup.bat to call the set_vsprefix_envs.bat Yonghong Zhu
2016-10-28 4:43 ` [Patch 3/3] BaseTools:introduce PREFIX env for VS tool path Yonghong Zhu
2016-11-01 2:51 ` Gao, Liming [this message]
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=4A89E2EF3DFEDB4C8BFDE51014F606A14B49C7FA@shsmsx102.ccr.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