I have prepared a small patch to fix the X11 test.This prevents errors like this:http://open.cdash.org/testDetails.php?test=153601982build=2442103
TestsX11HelloWorldX11.patch
Description: Binary data
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
Claus Klein wrote:
I have prepared a small patch to fix the X11 test.
This prevents errors like this:
http://open.cdash.org/testDetails.php?test=153601982build=2442103
Good catch. Patch pushed to next:
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=10e993f
Let's see what happens.
Eike
/opt/local/bin/gmake ExperimentalUpdate
Site: claus-kleins-macbook-pro.local
Build name: Darwin-i386-apple-darwin9-g++-mp-4.7
Updating the repository: /Users/clausklein/Downloads/cmake
Use GIT repository type
Old revision of repository is:
3bbba2ab2e6a733db6e0949fb5636a6ab9f59649
This helps:
git remote add origin git://cmake.org/cmake.git
On 15.07.2012, at 18:21, Claus Klein wrote:
What is wrong?
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the
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:
2012/7/12 David Cole david.c...@kitware.com:
I pushed this to 'next' the other day, but the test failures on dashmacmini3
remain, so the latest commit is not having its intended effect.
Back to Bill's original assertion:
I am not sure how this works on a fresh build tree either as cpack