bin
directory. We already had a compiler for x86 in the bin
directory, so we added subdirectories x86_ia64
and x86_amd64
for compilers that run on x86 and target 64-bit platforms as well as an amd64
directory for compilers that run on x64.%ProgramFiles(x86)%Microsoft Visual Studio2017EnterpriseVC
. (Note that this directory, %VCINSTALLDIR%
, changed from its VS 2015 location of %ProgramFiles(x86)%Microsoft Visual Studio 14VC
.)vcvars*.bat
scripts used to configure developer environments.%VCINSTALLDIR%
directory depending on feedback and requirements from internal and external developers.MSVC
. If you installed the “Clang with Microsoft Codegen” option, you’ll see a directory next to MSVC
called ClangC2
that contains the Clang/C2 binaries.%VCINSTALLDIR%
directory in VS 2015: bin
, crt
, include
, and lib
.MSVC
directory means that the Visual C++ tools can sit beside another toolset, in this instance, ClangC2
. Second, the fact that the tools are versioned inside of the MSVC
directory means that we can have multiple versions of the Visual C++ compiler installed on the same build machine. Right now, there’s no simple way to install multiple versions. But we’ve designed the directory structure to make it possible in the future to easily switch between versions of the Visual C++ tools.14.10.24629bin
directory. While in VS 2015 the x86 toolset was the “standard” toolset and we had directories with names like amd64_arm
representing the AMD64-ARM cross-targeting compiler, in VS 2017 these have been split up into directories labelled HostXXX
and a subdirectory called x86
or x64
. What’s the distinction here?amd64_arm
included the compilers that were hosted on x64, and targeted ARM. In VS 2017 it’s more structured: all of the x64 hosted compilers live in a directory called HostX64
. In that directory we find x86
, x64
, etc., indicating the target architecture.bin
directory is the only one with a set of HostXXX
directories. This is because the executables need to run on the host. The include
directory, which contains only source files, is specific to neither the host nor the target. The lib
directory is specific to only the target architecture. Likewise, many of the tools in the Auxiliary
directory are specific to the target architecture but not to the host.Program Files(x86)
directory. Visual C++ SDKs (such as the DIA SDK) will continue to be installed alongside the VC++ toolset.%VCINSTALLDIR%AuxiliaryBuildMicrosoft.VCToolsVersion.default.txt
, that contains the version string for the default toolset installed with VS. In a typical Preview 5 installation, %VCINSTALLDIR%
would point to %Program Files(x86)%Microsoft Visual StudioVisual Studio 15.0Common7IDEVisualCpp
.vcvars32.bat
when it launches. This issue has been fixed for the next release. In the interim, please launch a developer command prompt from the Windows shell, e.g., from the Start button or by pinning it to your Taskbar.