public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: Rebecca Cran <rebecca@bluestop.org>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH 0/1] Use the Windows Kits directory in 32-bit ProgramFiles, since none exists in 64-bit one
Date: Tue, 13 Dec 2016 05:57:16 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14D6A43DF@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20161213023243.8460-1-rebecca@bluestop.org>

Rebecca:  
  Please use VS2015x86 tool chain tag when windows is 64bit. VS2015 tool chain tag is used for 32bit windows. 

Thanks
Liming
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Rebecca Cran
> Sent: Tuesday, December 13, 2016 10:33 AM
> To: edk2-devel@lists.01.org
> Subject: [edk2] [PATCH 0/1] Use the Windows Kits directory in 32-bit
> ProgramFiles, since none exists in 64-bit one
> 
> On a fresh install of Windows 10 and Visual Studio 2015 etc., "C:\Program
> Files\Windows Kits"
> doesn't exist - only "C:\Program Files (x86)\Windows Kits" does. I don't know
> about 32-bit Windows, but since at this point 64-bit should be most common,
> update the path to the Windows SDK 8.1.
> 	
> Rebecca Cran (1):
>   Use the Windows Kits directory under the 32-bit Program Files
> 
>  BaseTools/Conf/tools_def.template | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> --
> 2.11.0.windows.1
> 
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


      parent reply	other threads:[~2016-12-13  5:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-13  2:32 [PATCH 0/1] Use the Windows Kits directory in 32-bit ProgramFiles, since none exists in 64-bit one Rebecca Cran
2016-12-13  2:32 ` [PATCH 1/1] Use the Windows Kits directory under the 32-bit Program Files Rebecca Cran
2016-12-13  5:57 ` 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=4A89E2EF3DFEDB4C8BFDE51014F606A14D6A43DF@SHSMSX104.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