VS2017的x64和ARM开发人员提示在哪里？

我安装了Visual Studio 2017 Build Tools.安装后,在导航开始→程序→Visual Studio 2017→Visual Studio工具时,只有一个x86开发人员命令提示符.没有x64和ARM的提示.(通常有大约6个开发人员提示可供选择).

x64和ARM的构建工具位于何处？

更新(JAN-18-2017)

安装整个Windows 10 SDK,根据@ magicandre1981指令构建15003后,我找不到Developer Prompts.我在"开始"菜单中找不到它们; 并放入Git Bash shell并搜索它们返回0结果.

在下面的名称中,vsdevcmd.bat是VC++ Build Tools for 2017 vcbuildtools.bat安装的内容.是VC++ Build Tools for 2015安装的内容.

MINGW64 /c/Program Files (x86)/Windows Kits/10
$ find . -iname 'vsdevcmd.*'

$ find . -iname 'vcbuildtools.*'

$ find . -iname '*.bat'

$ find . -iname '*.cmd'
./bin/10.0.15003.0/arm/SecureBoot/DeleteKitsPolicy.cmd
./bin/10.0.15003.0/arm/SecureBoot/InstallKitsPolicy.cmd
./bin/10.0.15003.0/arm64/install-sampleprovider.cmd
./bin/10.0.15003.0/arm64/uninstall-sampleprovider.cmd
./bin/10.0.15003.0/x64/install-sampleprovider.cmd
./bin/10.0.15003.0/x64/uninstall-sampleprovider.cmd
./bin/10.0.15003.0/x86/DismFoDInstall.cmd
./bin/10.0.15003.0/x86/GenerateUnionWinMD.cmd
./bin/10.0.15003.0/x86/install-sampleprovider.cmd
./bin/10.0.15003.0/x86/uninstall-sampleprovider.cmd
./bin/arm/SecureBoot/DeleteKitsPolicy.cmd
./bin/arm/SecureBoot/InstallKitsPolicy.cmd
./bin/arm64/install-sampleprovider.cmd
./bin/arm64/uninstall-sampleprovider.cmd
./bin/x64/install-sampleprovider.cmd
./bin/x64/uninstall-sampleprovider.cmd
./bin/x86/DismFoDInstall.cmd
./bin/x86/GenerateUnionWinMD.cmd
./bin/x86/install-sampleprovider.cmd
./bin/x86/uninstall-sampleprovider.cmd
./Debuggers/x64/srcsrv/cv2http.cmd
./Debuggers/x64/srcsrv/cvsindex.cmd
./Debuggers/x64/srcsrv/p4index.cmd
./Debuggers/x64/srcsrv/ssindex.cmd
./Debuggers/x64/srcsrv/svnindex.cmd
./Debuggers/x64/srcsrv/tfsindex.cmd
./Debuggers/x64/srcsrv/vssindex.cmd
./Debuggers/x64/srcsrv/walk.cmd
./Debuggers/x86/srcsrv/cv2http.cmd
./Debuggers/x86/srcsrv/cvsindex.cmd
./Debuggers/x86/srcsrv/p4index.cmd
./Debuggers/x86/srcsrv/ssindex.cmd
./Debuggers/x86/srcsrv/svnindex.cmd
./Debuggers/x86/srcsrv/tfsindex.cmd
./Debuggers/x86/srcsrv/vssindex.cmd
./Debuggers/x86/srcsrv/walk.cmd
./Windows Performance Toolkit/gpuview/log.cmd
./Windows Performance Toolkit/gpuview/log_mem.cmd
./Windows Performance Toolkit/WdfPerfEnhancedVerifier.cmd

$

出于绝望,我复制了2017 Build Tools Developer Prompt(适用于x86),并添加amd64_arm了2015 build工具.它导致失败:

[ERROR:parse_cmd.bat] Invalid command line argument: 'amd64_arm'. Argument will
be ignored.
**********************************************************************
** Visual Studio 2017 RC Developer Command Prompt v15.0
** Copyright (c) 2016 Microsoft Corporation
**********************************************************************
[ERROR:VsDevCmd.bat] *** VsDevCmd.bat encountered errors. Environment may be inc
omplete and/or incorrect. ***

C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools>

更加绝望......我开始使用进程监视器跟踪msiexec安装程序,并使用7-zip检查MSI内容.我能说的最好,即使在Developer Tools MSI安装程序中也没有开发人员提示:

开发人员提示bat文件似乎已经在VS 2017中进行了一些重组.现在,您可以更加自定义它,而不是使用一组固定的预定义开发人员提示.

要获取开发人员提示,例如arm,请添加-arch=arm -host_arch=amd64为参数VsDevCmd.bat(例如,在开始菜单的快捷方式中).

有关可用选项的完整列表,请查看\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\Tools\vsdevcmd\core\parse_cmd.bat或致电"\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\Tools\vsdevcmd" -help.

我不确定这是否真的记录在任何地方,或者是否会为VS 2017的最终版本更好地修复和/或记录.

安装内部预览Windows 10 SDK与此无关; 独立的Windows SDK不包含任何编译器,仅包含头文件和链接库.