|
Clang on Windows has an official installer here: http://llvm.org/releases/3.9.0/LLVM-3.9.0-win64.exe. But from what I can tell, it assumes that the user has some form of Visual Studio installed.
Not sure if the "community edition" works, but it does seem to be looking for header files in Visual Studio-related places.
I managed to compile and run a simple program using MSYS2's clang, but my Windows 10 machine failed to execute the generated binary, complaining that it "wasn't compatible".
/Jesper
From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Doug Schaefer <dschaefer@xxxxxxxxxxxxxx>
Sent: Tuesday, November 8, 2016 4:21 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] llvm build support on Windows
MSYS2 has clang 3.8 in it’s repo. That’s likely a safer place to get it.
BTW, MSYS2 is really good on Windows. I wish it had a GUI package manager, but maybe that’s will come out of the woodwork some day.
Doug.
Where did you get clang from Windows from. Is there an official distribution?
I'm still trying to figure out how to get clang to work at all on Windows. There are no libc or libstdc++ headers included, so presumably I need to pull in some combination of mingw and/or cygwin for this.
At the very least I should be able to update the documentation a bit on this when I finally get things to work.
/Jesper
I don't remember testing it on Windows, only on Mac. It's possible that it never really worked well on Windows. I also think the integration should just be about LLVM + Clang. The other combinations add more to the confusion and I think using the GCC front-end
was a stop gap solution until Clang became more mature.
I agree that supporting LLVM+Clang installed with the installer would be the best!
If you need to query the registry, you can look at org.eclipse.cdt.internal.core.Cygwin for an example.
Marc-André
I spent some time yesterday trying to familiarize myself with the code, but got confused with all the different variants of llvm + gcc + clang + mingw + cygwin. For some reason, I cannot get the CDT new project wizard to consider the LLVM toolchain to be
"supported" on my machine, and it looks like it is the toolchain's "target platform" which is considered "not compatible". That was about as far as I got yesterday.
I've managed to get things to work on Linux, but do we have any idea about how much of this stuff is expected to work on Windows? One use-case I'd like to address is when the user just has LLVM+Clang installed (using LLVM:s own windows installer) and no
mingw/cygwin, and automatically detect the LLVM installation using the registry.
Getting lldb to work out-of-the-box would also be very nice.
/Jesper
+1. I also wonder about all the different LLVM combos. This should really be a clang integration.
BTW, with the new Core Build, I’m getting away with including clang as a GCC toolchain. Seems to be very comparable in every way. I wonder if that’s a simplification we can make for managed build too.
Anyway, as M-A said, any love here would be appreciated :).
Doug.
Ok, good.
/Jesper
Hi Jesper,
The LLVM-toolchain definitely needs some love. I am not a LLVM expert but I have built it several times from source so I can definitely test and review your patches. As long as there is good explanation in the commit messages there shouldn't
be any problems.
Marc-Andre
Hi,
I wanted to see if I could set up a CDT-on-windows environment without using gcc/mingw/etc and got stuck on the LLVM-toolchain not detecting my LLVM-installation. Looking at the git history of the org.eclipse.cdt.managedbuilder.llvm.ui, there didn't seem
to be much activity there.
So, if I want to make the LLVM toolchain be a bit more Windows-friendly, should I just start hacking and hope that someone will review my patch, or is there someone I should coordinate with first?
/Jesper
|
