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

Devin Crumb bitogre at gmail.com
Mon Nov 11 11:20:57 PST 2013


Ok, that sounds like something I can do to start down the path of achieving
my goal.

Does Clang have C headers and C libraries for Unix that I can port to
Windows or do I need to start from scratch?

Devin Crumb


On Mon, Nov 11, 2013 at 1:53 PM, Reid Kleckner <rnk at google.com> wrote:

> On Mon, Nov 11, 2013 at 10:32 AM, Devin Crumb <bitogre at gmail.com> wrote:
>
>>
>> On Mon, Nov 11, 2013 at 1:24 PM, Chandler Carruth <chandlerc at google.com>wrote:
>>
>>> On Mon, Nov 11, 2013 at 10:16 AM, "C. Bergström" <
>>> cbergstrom at pathscale.com> wrote:
>>>
>>>> *My* view is that both a Mingw* and MSVC toolchain alternative is
>>>> absolutely necessary.
>>>>
>>>
>>> Sure. However, as you point out, you aren't contributing any patches in
>>> this direction.
>>>
>>
>> While Bergström may not be contributing patches in this direction, this
>> is a direction I would like to contribute patches for.  But, as this is the
>> first Open project that I am looking to contribute to, I am looking for
>> information on how to contribute in the direction I am interested in.  So
>> any help I can get in learning the right way to do this would be greatly
>> appreciated.
>>
>
> If you want a toolchain completely independent of either MSVC or mingw,
> you'd need more than just patches to clang and LLVM.
>
> Yaron gave a complete list of things you'd need, and the big thing that's
> missing is a C library subproject.  Without adding this to LLVM, you will
> always need either mingw or MSVC for C headers and C libraries.
>
> So far as I know, no one has plans to create or integrate another C
> library, and I don't see any reason to create a third environment.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20131111/bbdd783f/attachment.html>


More information about the cfe-dev mailing list