[cfe-dev] anyone knows the current state of libc++ on windows?

Yaron Keren yaron.keren at gmail.com
Thu May 8 05:59:34 PDT 2014


I think it mostly works, but not 100%.

Why use the combination of: clang compiler & Visual C++ link & Visual C++ C
headers & libcxx C++ headers ?


2014-05-08 15:28 GMT+03:00 Dennis Luehring <dl.soluz at gmx.net>:

> Am 08.05.2014 14:24, schrieb Yaron Keren:
>
>  clang can function in two different modes on Windows, MinGW compatible or
>> Visual C++ compatible.
>> The object formats are not compatible. The Windows installer for LLVM
>> includes a clang toolchain for Visual C++.
>> There is no ready MinGW-based current clang toolchain available, some
>> based
>> on older clang.
>>
>> What are you trying to achieve?
>>
>
> i just want to find out if its possible to get rid of MingGW using only
> clang & msvc-link & libc++ & MSVCRT
> or if there is much more work needed
>
>
>
>
>>
>>
>> 2014-05-08 14:35 GMT+03:00 Dennis Luehring <dl.soluz at gmx.net>:
>>
>> > Am 08.05.2014 13:07, schrieb Yaron Keren:
>> >
>> >  clang (lld) can't link .o files (COFF) on Windows.
>> >> MinGW is needed mainly for ld linker and for the C library headers but
>> >> also
>> >> for other libraries, such as the unwinder.
>> >>
>> >
>> > using the MSVC linker would solve llds problem with COFFs - and the
>> > Microsoft headers seems to be useable by clang
>> > but i don't known the differences between MinGW C lib headers and
>> > microsoft and what is needed for the unwinder
>> >
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20140508/234f27a1/attachment.html>


More information about the cfe-dev mailing list