[cfe-dev] What are the plans for creating a Windows Binary Release of Clang?

[Devin Crumb]

It looks like Clang.org links back to llvm.org/builds which indicates that
the build "integrates with MSVC 2010 and 2012."  That is a problem for me
as I only have MSVC 2008 and am unwilling to buy a newer version of MSVC (it
is just cost too much).  In fact, one of the reasons I am looking at Clang
is to get access to a non-GPL and non-proprietary compiler and toolchain
that runs on Windows.

I am willing to help make that happen but I do not know where to get
started with this specific effort.  So I am trying to figure out, is anyone
already trying to get Clang to be able build itself and be independent of
any GPL and/or proprietary software on Windows (with the exception of the
Windows OS itself).  If no one is currently working on this, what do I need
to do to start this effort with support from the Clang community?

>From some responses I have received from Yaron, it looks like I will need
to use Mingw until this goal is accomplished.  That is fine for now, so
long as there is a plan to eventually make Clang independent.  But, if the
Clang community is against this goal, I would like to know why?

Devin Crumb


On Mon, Nov 11, 2013 at 10:01 AM, Alp Toker <alp at nuanti.com> wrote:

> Hello Devin,
>
> We're producing a Windows version of clang at http://clang.org
>
> These unofficial builds are updated QA'd daily in the run up to 3.4, and
> the focus to package clang as a tooling SDK.
>
> This is mainly trunk, with the patches for bugfixes applied that haven't
> completed review yet (MemoryBuffer mmap fix, RTTI mangling error fix for
> MSVC ABI etc.) The patches used can all be found on the bug tracker or
> here mailing list.
>
> The package is built on Visual Studio 2013 / Windows 8.1 in C++11 mode
> so currently doesn't run on Windows XP -- the aim is to see how this
> will work out as there's been a debate lately on MSVC versions to support.
>
> Today's build includes the C# binding and a new Windows AST viewer
> (Clang Explorer) to help make the package more accessible to beginners.
> Python / Node.js bindings are lined up for tomorrows build.
>
> The main difference from the installer on LLVM.org is that this one is
> dedicated to the clang frontend and aims to test and stabilise the
> latest patches, and is code signed for use in a corporate environment etc.
>
> Alp.
>
>
>
> This includes the current set of Windows patches
> On 11/11/2013 13:14, Devin Crumb wrote:
> > Hello,
> >
> > I am new to Clang.  Over the weekend, I followed the instructions for
> > building Clang on Windows but because of some issues with the Visual
> > Studio 2008 libraries, I had to modify the Visual Studio 2008
> > libraries to get Clang to build.  Ideally, I would like to see the
> > Windows version of Clang get to the point where you can use Clang to
> > build itself and we have a binary release of Clang available for
> > people to use for other projects.
> >
> > Are there any existing plans produce a binary release of Clang for
> > Windows and to get Clang and related build tools to the point where
> > Clang is the compiler of choice for building Clang on Windows?  If
> > there is, where can I find that plan and how can I help?  If not, what
> > needs to happen to create such a plan?
> >
> > Devin Crumb
> >
> >
> > _______________________________________________
> > cfe-dev mailing list
> > cfe-dev at cs.uiuc.edu
> > http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>
> --
> http://www.nuanti.com
> the browser experts
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20131111/47f3b041/attachment.html>