MSBuild Integration files for drop-selecting LLVM as a toolchain in Visual Studio

Reid Kleckner rnk at google.com
Tue Aug 27 15:16:41 PDT 2013


It seems reasonable for these to have DOS line endings.  Do they need to
have a BOM, though?

+    <ClangInstallDir>$(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\LLVM\LLVM
3.4.svn)</ClangInstallDir>

Should this be looking for "LLVM 3.4.svn" specifically, or is there a way
to be more generic?

+
 <ExecutablePath>$(ClangInstallDir)\bin;$(ExecutablePath)</ExecutablePath>

We should probably add a new directory like msbuild-bin instead, since we
really don't want to place a clang binary named cl.exe into bin/.



On Tue, Aug 27, 2013 at 3:05 PM, Warren Hunt <whunt at google.com> wrote:

> Attached is a patch with the requisite files to integrate a
> drop-selectable llvm tool-chain in Visual Studio.  The files need to be
> copied to:
>
> C:\Program Files
> (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\Win32\PlatformToolsets\llvm
> on a 64 bit machine
>
> or
>
> C:\Program
> Files\MSBuild\Microsoft.Cpp\v4.0\Platforms\Win32\PlatformToolsets\llvm
> on a 32 bit machine
>
> or wherever MSBuild is installed.  This information can be obtained from
> the registry if desired.
>
> -Warren
>
>
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20130827/c1ee54d9/attachment.html>


More information about the llvm-commits mailing list