On 7/16/2012 8:07 PM, Richard Wackerbarth wrote:
With Ninja I have to look what happens. something goes still wrong.
I have a ctest script that pulls and builds ninja before building CMake.
You can see it here:
http://open.cdash.org/viewNotes.php?buildid=2448273
-Bill
--
Powered by
done
http://public.kitware.com/Bug/view.php?id=13418
Thanks for help
Claus
On 17.07.2012, at 02:07, Richard Wackerbarth wrote:
RE: The arch test, et.al. You should file a bug against CMake if a
test is failing only because the compiler does/does not produce the
same results as a compiler
On 7/15/2012 4:38 PM, Claus Klein wrote:
Can anyone please help?
To setup nightly builds follow the instructions here:
http://www.cmake.org/cmake/resources/testing.html
You should have the correct environment set before cmake is run. This
means PATH and CC, and CXX should be set correctly.
David,
Thanks for help, it works just with Makefile generator.
With Ninja I have to look what happens. something goes still wrong.
You may see http://open.cdash.org/viewTest.php?onlyfailedbuildid=2445267
my first working results.
With this 3 failed tests I have a problem:
They should not run
Richard,
It is not clear to me how to setup a nightly build.
I prefer a Clean build.
I would setup simply a new working every night at /var/tmp:
mkdir nightly nightly
git clone git://cmake.org/cmake.git
git remote add origin git://cmake.org/cmake.git
git checkout -b nightly
Can anyone please help?
Thanks in advance
Best Regards
Claus
On 09.07.2012, at 18:52, Claus Klein wrote:
Perhaps I must set a different CMAKE_SYSTEM_NAME, but which one?
#FIXME -DCMAKE_SYSTEM_NAME=Darwin-GNU \
-DCMAKE_C_COMPILER=/opt/local/libexec/ccache/gcc \
Claus,
You would use just Nightly -- the remaining Nightly* dashboard types
listed just do the named individual steps of a full Nightly dashboard,
not the whole thing.
However, if you are going to submit a nightly dashboard, you should do
so by following the directions found here:
Hi Richard,
it would be nice if you may setup a nightly build on darwin with
current MacPorts gcc-4.7 like this:
claus-kleins-macbook-pro:CmakeMakeBuildDir clausklein$ i386-apple-
darwin9-gcc-4.7.1 --version
i386-apple-darwin9-gcc-4.7.1 (MacPorts gcc47 4.7.1_1) 4.7.1
Copyright (C) 2012
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?onlyfailedbuildid=2423850
It is not clear to me
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=152892528build=2424062
I tried to check if ninja works now on Darwin, but some tests still
fails.
I use this configuration, but I have the gcc-4.7 installed too under /
opt/local/bin.
/usr/local/bin/cmake -G Ninja -DCMAKE_TEST_GENERATOR:STRING=Ninja \
-DCMAKE_TEST_MAKEPROGRAM:FILEPATH=${MAKECOMMAND} -
Hi Claus,
Have a look here: http://kennethreitz.com/xcode-gcc-and-homebrew.html
I advice you to install the Apple command line tools for xcode and
stop to use gcc.
Cheers,
Nico
On Sat, Jul 7, 2012 at 8:58 PM, Claus Klein claus.kl...@arcormail.de wrote:
I tried to check if ninja works now on
Thanks Nico,
I can live with the tools installed with mac ports.
I only tried to test Ninja with Cmake. And it works fine for me.
I will ignore this 5 errors while cmake selftest. ;-)
All other thinks I works with do fine without xcode ...
But IMO, cmake should use the configured tool chain
13 matches
Mail list logo
