<div dir="ltr">Which strange errors? If you are trying to build a C++ project, remember that Clang does not yet support exception handling and you should disable them. To do this, <span style="font-family:arial,sans-serif;font-size:13px">you should go to Project Properties and navigate to Configuration Properties, C/C++, Command Line, Additional Options and put /GR- /D_HAS_EXCEPTIONS=0 there.</span><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">If it builds a 32-bit binary, it should succeed with 64-bit, since the toolset is exactly the same, with the difference of the parameters passed to clang-cl.exe.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 29, 2014 at 9:26 PM, Eric Mader <span dir="ltr"><<a href="mailto:emader@gmx.us" target="_blank">emader@gmx.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
I replaced all instances of "$(Platform)" with "x64" for the x64
.props file and it still fails, so it looks like that guess was
wrong as well.<br>
<br>
Regards,<br>
Eric<div><div class="h5"><br>
<br>
<div>On 9/29/14, 2:11 PM, Eric Mader wrote:<br>
</div>
<blockquote type="cite">
Quoting doesn't seem to make a difference. Strangely, the Win32
toolset seems to work. (Where "work" means that clang runs and
produces a bunch of strange errors ;-)<br>
<br>
The only difference I see between the two .props files is that one
passes "-m86" to the compiler and the other one passes "-m64".<br>
<br>
They both reference $(Platform), so I wonder if maybe $(Platform)
isn't getting set correctly? The platform name in the project is
"x64" which seems right...<br>
<br>
Regards,<br>
Eric<br>
<br>
<div>On 9/29/14, 12:40 PM, Rafael Auler
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Your install dir has a whitespace. Have you tried
quoting? e.g. <span style="font-family:arial,sans-serif;font-size:13px"> <LLVMInstallDir>"C:\Program
Files (x86)\LLVM"</LLVMInstallDir></span>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px">Best
regards,</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px">Rafael
Auler</span></div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Sep 29, 2014 at 7:38 PM, Eric
Mader <span dir="ltr"><<a href="mailto:emader@gmx.us" target="_blank">emader@gmx.us</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> I changed
tooset-vs2013.props to this:<br>
<br>
<Project xmlns=<a href="http://schemas.microsoft.com/developer/msbuild/2003" target="_blank">"http://schemas.microsoft.com/developer/msbuild/2003"</a>>
<br>
<Import
Project="$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v120\Microsoft.Cpp.$(Platform).v120.props"Condition="Exists('$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v120\Microsoft.Cpp.$(Platform).v120.props')"/><br>
<Import
Project="$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v120\Toolset.props"Condition="Exists('$(VCTargetsPath)\Platforms\$(Platform)\PlatformToolsets\v120\Toolset.props')"/><br>
<br>
<PropertyGroup><br>
<LLVMInstallDir>C:\Program Files
(x86)\LLVM</LLVMInstallDir><br>
<ExecutablePath>"$(LLVMInstallDir)\msbuild-bin";$(ExecutablePath)</ExecutablePath><br>
<LibraryPath>$(LLVMInstallDir)\lib\clang\3.6.0\lib\windows;$(LibraryPath)</LibraryPath><br>
</PropertyGroup><br>
<br>
<ItemDefinitionGroup><br>
<ClCompile><br>
<!-- Set the value of _MSC_VER to claim for
compatibility --><br>
<AdditionalOptions>-m64 -fmsc-version=1800
%(AdditionalOptions)</AdditionalOptions><br>
</ClCompile><br>
</ItemDefinitionGroup><br>
</Project><br>
<br>
It still doesn't work... Is there something else I need
to change?<br>
<br>
Regards,<br>
Eric
<div>
<div><br>
<br>
<div>On 9/29/14, 10:41 AM, Rafael Auler wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">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).</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Sep 29, 2014 at
5:33 PM, Eric Mader <span dir="ltr"><<a href="mailto:emader@gmx.us" target="_blank">emader@gmx.us</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> I
copied the x64 toolsets by hand and now
when I try to compile a file, I get an
error message saying that the build tools
for llvm-2013 cannot be found. I guess
that this is because the installer didn't
correctly add the LLVM tools to $PATH. How
can I correctly add the LLVM tools to the
path?<br>
<br>
Regards,<br>
Eric
<div>
<div><br>
<br>
<div>On 9/29/14, 10:22 AM, Eric Mader
wrote:<br>
</div>
<blockquote type="cite"> Ah, OK. I did
find the install.bat script and ran
it in a command shell w/ admin
access. I have VS 2010 and VS 2013
installed. The script reported that
it copied 6 files. Poking around, I
noticed that it wrote toolsets only
for win32. (vs2010, vs2013,
vs2113_xp) Looking at the script, it
seems like it should write x64
toolsets too. I'll try copying the
x64 toolsets by hand to see what
happens<br>
<br>
Regards,<br>
Eric Mader<br>
<br>
<div>On 9/29/14, 9:38 AM, Rafael
Auler wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">I was not
necessarily asking you to build,
but just to check your
installation folder and see
whether you have
"tools/msbuild/install.bat"
there because I don't know if
the Windows installer puts this
there. However, if you want to
build outside VS, I recommend
mingw-w64. If you have any
difficulties about the VS build
process though, feel free to ask
questions :-)
<div><br>
</div>
<div>Usually, to build LLVM on a
Windows system from scratch
(with VS installed), I would
just install git for windows,
which already installs a lot
of important GNU tools, and
ask to put everything in my
path. Then I would install
CMake and put this in my path.
Afterwards, open a shell with
VS paths, create a build
folder, run CMake -G"Visual
Studio ...<yourversion>"
and then "msbuild <name of
project>". A lot of people
prefer to use ninja instead of
msbuild, though, but you must
install ninja and use CMake
-GNinja instead.</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon,
Sep 29, 2014 at 4:29 PM, Eric
Mader <span dir="ltr"><<a href="mailto:emader@gmx.us" target="_blank">emader@gmx.us</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> I was
hoping to not have to
build LLVM myself,
especially on Windows. Can
anybody help me with the
Windows installer?<br>
<br>
Failing that, I find the
directions for how to
compile on Windows hard to
follow? Can I build using
Cygwin?<br>
<br>
Regards,<br>
Eric
<div>
<div><br>
<br>
<div>On 9/29/14, 8:11
AM, Rafael Auler
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">I'm
not sure about the
Windows installer,
but if you build
and install LLVM
for Windows from
the source code,
you should be able
to go to the
installation
folder, find a
subfolder named
"tools/msbuild"
and run the
"install.bat"
script. This
should make your
LLVM toolset
appear in VS.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On
Mon, Sep 29,
2014 at 2:52 PM,
Eric Mader <span dir="ltr"><<a href="mailto:emader@gmx.us" target="_blank">emader@gmx.us</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I’m
trying to
install
LLVM-3.6.0-r218288-win32.exe
on Windows 7
Ultimate x64.
The install
doesn’t
complain, but
the toolset
doesn’t show
up in either
Visual Studio
2013 or Visual
Studio 2010.
Also I
selected the
choices to add
LLVM to the
path for every
user and put
an LLVM icon
on the
desktop.
Neither of
this happened.
Can anyone
tell me how to
get this to
work?<br>
<br>
Regards,<br>
Eric Mader<br>
_______________________________________________<br>
LLVM
Developers
mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu" target="_blank">LLVMdev@cs.uiuc.edu</a>
<a href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div>