title: Visual Studio Community 2017 cl.exe
body: <p>I am working on compiling some CUDA kernels on a Windows system.  From my understanding, the <code>nvcc</code> compiler requires the use of <code>cl.exe</code> to compile on Windows systems.  The primary way to get this is with Visual Studio.  I have therefore installed the <a href="https://www.visualstudio.com/vs/community/" rel="noreferrer">free community edition</a>.  After which I expected there to be the <code>bin</code> directory within the <code>VC</code> directory as shown in multiple other questions such as <a href="https://stackoverflow.com/questions/8125826/error-compiling-cuda-from-command-prompt">this one</a> and <a href="https://stackoverflow.com/questions/37377487/nvcc-fatal-cannot-find-compiler-cl-exe-in-path-although-visual-studio-12-0-i">this one</a>.  And yet, I need to go to several layers deeper to find</p>
  
  <pre><code>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.10.25017\bin\HostX64\x64\cl.exe
  </code></pre>
  
  <p>This particular project is intended to make a program that can be compiled and used on multiple different Windows systems.  Do I really need to expect the <code>cl.exe</code> file to be this nested or did I miss some sort of installation step here?  I was expecting a shorter path:</p>
  
  <pre><code>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\bin\
  </code></pre>
  
  <p>Ultimately I need as simple a way as possible for users to be able to have their environment find the cl.exe file.  Generally this involves (at the highest level) setting an environmental variable.  </p>