On 9/29/2013 4:09 PM, Jim Bell wrote:

On 2013-09-29 2:54 PM, Beman Dawes wrote:

...

Chandler Carruth has asked for a volunteer to start running boost regression tests for the Clang on Windows project.

For more about this project, see http://blog.llvm.org/2013/09/a-path-forward-for-llvm-toolchain-on.html.

Chandler cornered me at the C++ committee meeting last week, and emphasized how much they would like to see boost tests passing using Clang in a Visual Studio environment. This would be a big plus for boost developers and users in the Windows environment IMO, so I hope we can help them out.

FWIW, I started on a Clang regression (using some mgw-w64 version), but quit when I found that it would only build static libraries, which caused a huge swath of tests to fail for that reason alone.

I don't recall it misbehaving badly in other cases, though I may not have looked too closely.

Really ? Try 'bjam toolset=clang" under Windows in the Boost preprocessor test directory.

On 9/30/2013 1:59 AM, Joshua Boyce wrote:

On Mon, Sep 30, 2013 at 8:54 AM, Edward Diener wrote:

...

On 9/29/2013 4:09 PM, Jim Bell wrote:

...

On 2013-09-29 2:54 PM, Beman Dawes wrote:

...

Chandler Carruth has asked for a volunteer to start running boost regression tests for the Clang on Windows project.

For more about this project, see http://blog.llvm.org/2013/09/**a-path-forward-for-llvm-** toolchain-on.htmlhttp://blog.llvm.org/2013/09/a-path-forward-for-llvm-toolchain-on.html .

Chandler cornered me at the C++ committee meeting last week, and emphasized how much they would like to see boost tests passing using Clang in a Visual Studio environment. This would be a big plus for boost developers and users in the Windows environment IMO, so I hope we can help them out.

FWIW, I started on a Clang regression (using some mgw-w64 version), but quit when I found that it would only build static libraries, which caused a huge swath of tests to fail for that reason alone.

I don't recall it misbehaving badly in other cases, though I may not have looked too closely.

Really ? Try 'bjam toolset=clang" under Windows in the Boost preprocessor test directory.

______________________________**_________________ Unsubscribe & other changes: http://lists.boost.org/** mailman/listinfo.cgi/boosthttp://lists.boost.org/mailman/listinfo.cgi/boost

Using toolset=clang on Windows still gives "clang-linux" for me, which needs to be fixed. We also need to distinguish between 'native' Clang and 'mingw-w64' Clang (see me other post) as they use an entirely different standard library and CRT.

There is no toolset other than 'clang' for using clang under Windows AFAIK. If a separate one is needed for clang under Windows then that's up to the Boost Build developers to provide one. I have no idea how to do so and am not proficient with Boost Build and bjam. I do know that if I use toolset=clang under Windows it seems to find the header files which it needs but I have no idea how it is doing so. I am invoking this from the normal Windows command processor and not from the MingW Linux-like command processor so it appears to be working for me. My build of clang for Windows was done through the source and followed the instructions at http://clang.llvm.org/get_started.html for using VS2010 for building the latest clang.

On Mon, Sep 30, 2013 at 6:09 AM, Jim Bell wrote:

On 2013-09-29 2:54 PM, Beman Dawes wrote:

...

Chandler Carruth has asked for a volunteer to start running boost regression tests for the Clang on Windows project.

For more about this project, see http://blog.llvm.org/2013/09/**a-path-forward-for-llvm-** toolchain-on.htmlhttp://blog.llvm.org/2013/09/a-path-forward-for-llvm-toolchain-on.html .

Chandler cornered me at the C++ committee meeting last week, and emphasized how much they would like to see boost tests passing using Clang in a Visual Studio environment. This would be a big plus for boost developers and users in the Windows environment IMO, so I hope we can help them out.

FWIW, I started on a Clang regression (using some mgw-w64 version), but quit when I found that it would only build static libraries, which caused a huge swath of tests to fail for that reason alone.

I don't recall it misbehaving badly in other cases, though I may not have looked too closely.

hth, -Jim

______________________________**_________________ Unsubscribe & other changes: http://lists.boost.org/** mailman/listinfo.cgi/boosthttp://lists.boost.org/mailman/listinfo.cgi/boost

I believe Chandler is talking about Clang using the 'native' libraries/headers/etc which is VERY different to using mingw-w64. Having test runners for both would be ideal, but a test runner for the 'native' case only would be preferable to the 'mingw-w64' case only (imo)...