[cmake-developers] cmake selftest use different compiler and binutils as configured on Darwin

[Claus Klein]

This thread is not about ninja.

Its about cmake self build and cmake self test after build!

I have same results with "Unix Makefiles" generator when I use the  
same toolchain;

http://open.cdash.org/testDetails.php?test=152892528&build=2424062
http://open.cdash.org/testDetails.php?test=152794057&build=2421596

The biggest problem is that ctest does not use my configured tools!
I have to restrict the exported path to handle that right?

Claus

On 08.07.2012, at 14:47, Richard Wackerbarth wrote:

> Gentlemen:
>
> If you think that you have something that is working on OSX with  
> ninja,
> we need to arrange to get it into "next" (assuming that it doesn't  
> break anything else)
> At this point, it would not be enabled (by default), but some of the  
> test systems on the nightly dashboard intentionally enable it to see  
> how well it fairs.
>
> I am currently running two OSX tests, both with cmake from the  
> "next" branch. One uses an older version of ninja that seemed stable  
> and the other uses the latest nightly sources from the ninja  
> repository.
>
> If we need to test some other configurations, just let me know which  
> repositories/branches I should use for testing.
>
> Richard
>
> On Jul 8, 2012, at 5:04 AM, Claus Klein wrote:
>> On 07.07.2012, at 21:34, Nicolas Desprès wrote:
>>
>>> I advice you to install the Apple command line tools for xcode and
>>> stop to use gcc.
>>
>> I have removed the path to /opt/local/bin and tested xcode without  
>> ninja:
>> http://open.cdash.org/viewTest.php?onlyfailed&buildid=2423850
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake-developers/attachments/20120708/56dcc546/attachment.html>