Subject: Re: [boost] ... broken with clang
From: Christopher Jefferson (chris_at_[hidden])
Date: 2011-12-19 10:58:02
On 19 Dec 2011, at 15:10, Francois Duranleau wrote:
> On Sat, Dec 17, 2011 at 10:57 AM, Mathias Gaunard
> <mathias.gaunard_at_[hidden]> wrote:
>> On 12/17/2011 04:48 PM, Beman Dawes wrote:
>>> On Sat, Dec 17, 2011 at 6:42 AM, Andrey Semashev
>>> <andrey.semashev_at_[hidden]> wrote:
>>>> ... All in all, I consider clang to be at a too early stage of
>>>> 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,
>> It's trivial to install on Mac OS X (comes with XCode).
>> It's also relatively easy to get it to work on Linux.
>> Why would it be required to use Windows to support clang? Surely you can get
>> ssh access to some linux or mac boxes.
> +1 to that. Plus, as development on embedded devices seriously picking
> up, and Clang happening to be the only compiler available to iOS
> developpers starting with iOS 5.0, it would be sad to have Boost to be
> so Windows-centric and only support compilers that only install/run
> well on Windows. I understand we need to run tests and all, but at
> least, Clang is not an iOS-only compiler, so it can be tested on Linux
> or Windows.
The most important thing is probably for people to run the boost regression tester with the compiler of their preference, and file bugs when things break. It's not hard to do, but it is a fairly high time investment unfortunately.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk