search for: platformtoolset

...mx.us> wrote: > I changed tooset-vs2013.props to this: > > <Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003" > <http://schemas.microsoft.com/developer/msbuild/2003>> > <Import > Project="$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v120\Microsoft.Cpp.$(Platform).v120.props" > Condition="Exists('$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v120\Microsoft.Cpp.$(Platform).v120.props')"/> > <Import > Project="$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v120\Tool...

...rops to this: >> >> <Project >> xmlns="http://schemas.microsoft.com/developer/msbuild/2003" >> <http://schemas.microsoft.com/developer/msbuild/2003>> >> <Import >> Project="$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v120\Microsoft.Cpp.$(Platform).v120.props"Condition="Exists('$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v120\Microsoft.Cpp.$(Platform).v120.props')"/> >> <Import >> Project="$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets...

Open the file toolset-vs2013.props and you'll understand what's happening and where the path is set. It tries to fetch the LLVM installation path from the Windows registry. Just fix this (maybe editing your registry or editing the .props file, whatever suits you best). On Mon, Sep 29, 2014 at 5:33 PM, Eric Mader <emader at gmx.us> wrote: > I copied the x64 toolsets by hand and

...Dec 2, 2013 at 1:55 PM, Reid Kleckner <rnk at google.com> wrote: > Getting the platform toolsets installed in the right place is a dirty job > handled by this script: > > http://llvm.org/viewvc/llvm-project/llvm/trunk/tools/msbuild/install.bat?view=markup > > Do you have a PlatformToolsets directory somewhere under > ProgFiles/MSBuild? If so, where is it? We can add it to the path search. > > If anyone has better ideas on how to find this magical directory, > suggestions are welcome. :) > > > On Thu, Nov 28, 2013 at 6:42 AM, Kelly Sommers <kell.sommers at...

Looks like the PlatformToolsets are cached in the .suo file. If you move it out of the way or delete it, VS will re-scan for toolsets. I'm not sure what other user state is stored there, though. That's annoying. =/ On Tue, Dec 3, 2013 at 6:37 AM, Kelly Sommers <kell.sommers at gmail.com>wrote: > Thanks fo...

We inject a typedef for size_t here: http://llvm.org/viewvc/llvm-project/cfe/trunk/lib/Sema/Sema.cpp?revision=218230&view=markup#l206 The typedef type is determined by calling getSizeType(). SizeType is (relevantly) calculated in two places: X86_64 http://llvm.org/viewvc/llvm-project/cfe/trunk/lib/Basic/Targets.cpp?revision=218666&view=markup#l3512 X86_32

>From this website: http://llvm.org/builds/ I've installed the LLVM toolchain on 2 Windows machines. One with Visual Studio 2012 and another with Visual Studio 2013. After installing the LLVM toolchain neither machine shows the LLVM option in the Visual Studio project properties pane where you can select which toolchain to use for the project. Am I missing a step somewhere? :) Thanks for

...Studio, select a project in Solution Explorer, open its Property Page (Alt+F7 by default), and in the "General" section of "Configuration Properties" change "Platform Toolset" to "LLVM-vs2010" or "LLVM-vs2012". Alternatively, invoke MSBuild with /p:PlatformToolset=LLVM-vs2012 to try out the toolchain without modifying the project files. At 2013-11-29 00:00:08,"Kelly Sommers" <kell.sommers at gmail.com> wrote: From this website: http://llvm.org/builds/ I've installed the LLVM toolchain on 2 Windows machines. One with Visual Studio...

Getting the platform toolsets installed in the right place is a dirty job handled by this script: http://llvm.org/viewvc/llvm-project/llvm/trunk/tools/msbuild/install.bat?view=markup Do you have a PlatformToolsets directory somewhere under ProgFiles/MSBuild? If so, where is it? We can add it to the path search. If anyone has better ideas on how to find this magical directory, suggestions are welcome. :) On Thu, Nov 28, 2013 at 6:42 AM, Kelly Sommers <kell.sommers at gmail.com>wrote: > From t...

On Fri, Jul 10, 2015 at 2:00 AM, Chandler Carruth <chandlerc at google.com> wrote: > This seems more relevant to cfe-dev. > Okay. > > You seem to be struggling with the need to name the binary 'cl.exe'. Last > time I checked, we installed clang-cl.exe under that name in a specialized > director specifically so you can use build systems relying on that name. >

...Default.props" /> + <PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Any|Win32'" Label="Configuration"> + <ConfigurationType>Utility</ConfigurationType> + <UseDebugLibraries>false</UseDebugLibraries> + <PlatformToolset>v140</PlatformToolset> + <WholeProgramOptimization>true</WholeProgramOptimization> + <CharacterSet>MultiByte</CharacterSet> + </PropertyGroup> + <Import Project="$(VCTargetsPath)\Microsoft.Cpp.props" /> + <ImportGroup Label="Ex...