[cmake-developers] [PATCH SET] Support of Clang/C2 compiler
Mariusz Pluciński
plucinski.mariusz at gmail.com
Sun Mar 27 20:31:09 EDT 2016
Hi,
Sorry for a bit late answer.
2016-03-09 15:37 GMT+01:00 Brad King <brad.king at kitware.com>:
> On 02/27/2016 09:38 AM, Mariusz Pluciński wrote:
> > Following is the list of patches with descriptions:
>
> Thanks!
>
You're welcome!
> > 11. Tests: do not build ExternalProjectLocal/TutorialStep5 when path is
> too long
> > This toolset uses a bit longer names of some files, which may cause full
> path size to exceed 256 characters.
>
> The condition for this one needs to be thought out a bit more.
> We no longer support Windows 98 so the old condition can simply
> be replaced. I expect it applies to all Windows versions anyway.
> Anyway, this is mostly orthogonal to Clang/C2 support.
>
In general it's orthogonal. The reason why I put it there was that in my
case, it was the switch to Clang/C2 that caused the issue. It seems that
when this toolkit is in use, some of the temporary files and directories
have a bit longer names. The direct cause for these failures was some of
.tlog files that got full path longer than 256 characters - when I moved
the project nearer to root directory, these were compiling successfully.
That said, rerunning this test in shorter path had succeeded. I don't know
if it's worth to modify the CMake code to detect such situation, although
these failures seem quite mysterious - the compiler or MSBuild just fails
without detailed error message.
> > 8. Tests: fix Module.WriteCompilerDetectionHeader building on Clang/C2
> > Visual Studio does not handle this test very well. Not sure why.
> >
> > 15. Tests: disable VSMidl on Clang/C2
> > I don't know why this test fails.
>
> I'm going to let these fail for now until someone has time to investigate
> them more.
>
I see. I didn't know, how do you handle that situations in CMake project.
>
> Would you be able to run nightly testing with this generator/compiler?
> Instructions are here:
>
> https://cmake.org/Wiki/CMake/Git/Dashboard
>
>
Sure I can. I have set it up today (
https://open.cdash.org/viewSite.php?siteid=17356 ), and now, it seems that
there're some more failures that I saw while running these tests before.
I'm going to take a look on them and fix them if I manage to do so.
Best Regards
Mariusz Plucinski
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20160328/a181e721/attachment.html>
More information about the cmake-developers
mailing list