News for hackers. Stuff that matters.

A comment on LLVM 3.8 Release Notes. Parent comment

Re:LLVM 3.8 Release Notes by tavert on Tuesday March 08, 2016 @04:29PM (#11248828)
That's unlikely to change any time soon, at least from the LLVM side. They're not really in the business of providing OS API headers. At least there's a Windows SDK download now that is smaller than the whole Visual Studio IDE, and the MinGW-w64 project is working on making fully LLVM-based toolchains more usable over time.
[ Parent | on HN ]
Re:LLVM 3.8 Release Notes by kozukumi on Wednesday March 09, 2016 @06:01AM (#11252195)
It would be nice if they could at least keep the documentation up to date on which MinGW-W64 builds work and which don't etc. I just don't have the time to muck around with things when I can just grab a MinGW build and it "just works" out of the box.

With how friendly Microsoft are getting with Clang I was hoping we might see a LLVM+MSVCHeaders build appear. I am sure it is possible considering the new MS.

I know I am lazy in wanting a one-click solution but my build environment is very important to me. I don't want to have to hack it together using blog posts from 6 months ago that might or might not give me a stable setup. I don't think it is too much to ask for something like TDM's GCC installer.

[ Parent | on HN ]
Re:LLVM 3.8 Release Notes by jibsen on Wednesday March 09, 2016 @11:09AM (#11253741)
You might like Clang with Microsoft CodeGen[1], a work in progress by Microsoft to add a Clang toolset to Visual Studio 2015 that uses the MSVC backend.

[1]: https://blogs.msdn.microsoft.com/vcblog/2015/12/04/clang-wit...

[ Parent | on HN ]
Re:LLVM 3.8 Release Notes by kozukumi on Wednesday March 09, 2016 @12:08PM (#11254127)
Yeah I have been following the Clang\C2 work. I guess that is what the LLVM project would rather work with Microsoft towards rather than rolling their own. It will certainly make life easier for cross-platform C++ to use Clang/C2 over C1/C2. Having to install Visual Studio to get it is a bit annoying though, I would prefer to fire up a VM with just Clang and the MSVC/Windows headers to command line compile. Visual Studio is a big install inside a VM which is annoying.

I quick question you may know the answer to, does the Windows SDK not come with the Windows C++ headers anymore? I installed the Windows 10 1511 SDK the other day but even a full install didn't give me any of the stdlib which I thought it would do? I understand they removed the compilers but I thought the headers still came with it?

[ Parent | on HN ]
Re:LLVM 3.8 Release Notes by tavert on Thursday March 10, 2016 @10:47PM (#11264523)
Oh, bummer, I even thought the Windows SDK still had the command-line compilers. What's it good for then?

Most open-source projects don't even bother supporting MSVC, and I don't blame them one bit. MinGW-w64 gives a significantly less painful route to Windows support, and allows you to pretend MSVC doesn't exist in a lot of cases.

[ Parent | on HN ]
Re:LLVM 3.8 Release Notes by kozukumi on Friday March 11, 2016 @03:12AM (#11265374)
I am trying to work out what use the Windows SDK is without Visual Studio (which also includes the Windows SDK!).
[ Parent | on HN ]
Re:LLVM 3.8 Release Notes by tavert on Thursday March 10, 2016 @10:44PM (#11264516)
What benefit does that really have over just using Clang with LLVM codegen though?
[ Parent | on HN ]