[cfe-dev] libc++ on Windows (Rationale)

Christopher Jefferson chris at bubblescope.net
Tue Aug 24 06:41:23 PDT 2010


On 24 Aug 2010, at 14:29, Fernando Pelliccioni wrote:

> On Tue, Aug 24, 2010 at 10:11 AM, Michael Spencer <bigcheesegs at gmail.com>wrote:
> 
>> On Tue, Aug 24, 2010 at 9:06 AM, Michael Spencer <bigcheesegs at gmail.com>
>> wrote:
>>> On Tue, Aug 24, 2010 at 8:03 AM, Fernando Pelliccioni
>>> <fpelliccioni at gmail.com> wrote:
>>>> Hi,
>>>> 
>>>> I am trying to compile LibC++ on WinXP (32) using MinGW (GCC 4.6).
>>>> 
>>>> I've seen some extensions are used, as the "xlocale.h", which makes it
>>>> difficult to compile in Windows using MinGW. No way to use MSVC.
>>>> 
>>>> I wonder..., What is the goal of the creators of Clang and LibC++ in
>> terms
>>>> of portability? Is there any reason why Windows should not be supported?
>> Or
>>>> just a matter of time, is started by the Unix-Like operating systems?
>>>> 
>>>> I would like to contribute to the project, to make Clang and LibC++, in
>> the
>>>> future, the default compiler C++ for almost any platform.
>>>> 
>>>> Thanks and greetings.
>>>> Fernando.
>>> 
>>> I too support this. There is currently no decent c++ stdlib for
>>> windows (sorry MinGW, but you don't count for me).
>>> 
>>> - Michael Spencer
>>> 
>> 
>> Sorry for the double post, but I just realized I needed to clarify
>> something.
>> 
>> I do not think that libc++ should attempt to be compatible with MSVC
>> where MSVC does not implement C++0x or makes things difficult. My main
>> concern is Clang+Windows compatibility when Clang gets C++0x support.
>> 
>> 
> Admittedly, I did not take into account C++0x.
> I support your opinion. The ideal option would be Clang+LibCxx in Windows as
> the default compiler.
> It would be a great goal.

I disagree. Any such compiler+library would be unable to link to any precompiled C++ code (which used the standard library) on Windows.

Chris



More information about the cfe-dev mailing list