On 17 December 2011 18:00, Eric Niebler <eric@boostpro.com> wrote:
On 12/17/2011 8:37 AM, Mateusz Łoskot wrote:
On 17 December 2011 15:48, Beman Dawes <bdawes@acm.org> wrote:
On Sat, Dec 17, 2011 at 6:42 AM, Andrey Semashev <andrey.semashev@gmail.com> wrote:
... All in all, I consider clang to be at a too early stage of development to support it in the libraries.
While I believe clang has a bright future, I'm afraid I agree with you.
Clang's lack of support on Windows, including lack of installer, makes it hard for Windows developers to work with clang.
Looking forward to the day when clang "just works" on Windows,
I haven't noticed any problems with building Clang for Windows. It's pretty straightforward process. <snip>
Ah, but have you successfully *used* clang on Windows? What std library did you link with? If you've managed this, please post a how-to here or somewhere accessible. Thanks,
Eric, your assumption hits the spot. When I was running a quick test of Clang with Boost under Windows, I built Clang without problems. Next, I tried to compile Boost and I had got the errors as reported in ticket #5943. So, I assumed it is Boost.Build issue and abandoned any further testing. At that time, I hadn't monitored Clang development closely, so I had no idea about the now well-known problems with ABI (RTTI, streams) between Clang and Visual C++ C/C++ Run-Time libraries. Later, I have seen some random notes about possible use of Apache STDCXX or even LLVM/libc++ with Clang on Windows, though nothing officially confirmed, so I decided to wait a bit. Also, I may be thoroughly wrong, but according to what I have seen on libc++ mailing list it seems to be targeting Windows through MinGW, MinGW is not my cup of tea, so not even tried it. It feels to me we have number of C++ std libraries being developed, but none included Clang on Windows support in near roadmap. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net