[cmake-developers] Initial Attempt at Green Hill MULTI IDE Generator Support
Brad King
brad.king at kitware.com
Fri Feb 20 10:35:09 EST 2015
On 02/19/2015 07:44 PM, Geoffrey Viola wrote:
> The nightly build that I use does use the "cmake_common.cmake" script
> to grab the latest code, build, test it, etc. Here's what my nightly
> build results look like: https://open.cdash.org/buildSummary.php?buildid=3701008.
Sorry, I mixed up your nightly build and the experimental build you linked.
> I made that small change in the attached patch.
> I ran another experimental build in debug. Here are those results:
> https://open.cdash.org/buildSummary.php?buildid=3701457.
Thanks.
> I expected the "CMakeOnly.MajorVersionSelection-PythonInterp_2" to fail
> because I have the Python 3.3 executable in my path.
Please add to your dashboard scripts a line like:
set(ENV{PATH} ...)
to set a path without python in it for running this dashboard.
That will avoid the problem, which is a separate discussion to
address. (The test is covering that the requested major version
is preferred if executables called "python2" and "python3" are
both in the path, but if just "python" is available then it is
used.)
> But I still get the "CMake.GetPrerequisites" test timing out.
I don't see that in:
https://open.cdash.org/buildSummary.php?buildid=3701966
> Also, I haven't debugged the warnings in the Build row yet.
That may be due to the lack of a fresh build tree:
#CTEST_EMPTY_BINARY_DIRECTORY(${CTEST_BINARY_DIRECTORY})
> This suit of tests was done using a script based on the
> autogenerated "CTestScript.cmake" script.
I don't think CDash has been configured to generate those for
CMake properly. Once you have the nightly dashboard submission
running cleanly then we can look at merging your generator for
testing in 'next' to have it covered there.
-Brad
More information about the cmake-developers
mailing list