>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 the help! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131128/eb393806/attachment.html>
pls read the page of http://llvm.org/builds/ : To use the LLVM toolchain from Visual 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 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 the help! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131202/799355bf/attachment.html>
Yeah I read that page. As I said in the original email, the option in the drop down (as you mentioned above - LLVM-vs2012) doesn't show up. It's like it's not installing properly? On Sun, Dec 1, 2013 at 8:03 PM, 孙成波 <sun_chengbo at 126.com> wrote:> pls read the page of http://llvm.org/builds/ : > > To use the LLVM toolchain from Visual 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 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 the help! > > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131201/4762c794/attachment.html>
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 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 the help! > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131202/9c35556e/attachment.html>
Thanks for the reply Reid! I took a look at that script and found that the files were properly copied so I poked around some more. I found that if I started a new win32 console application, LLVM shows up in the toolchain drop down! But if I open another project file from an existing project to see if it compiles in LLVM the dropdown options are missing! Do you know what might be deciding when the option appears? Is there another setting in the project that needs to be set? Thanks for the help! On Mon, 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 gmail.com>wrote: > >> 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 the help! >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >> >> >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131203/e0b4d89f/attachment.html>