Ok, we're in business now...

I'm not sure why this was not working before, but... THANKS!

I have to say, cdash is totally cool - I'm very impressed.

Now for a few (small) issues/questions:

- How do I set the Build Name (I guessed at CTEST_BUILD, but no.)
- I set up a project named "Qpid C++" and I can submit to it using
submit.php?project=Qpid%20C%2B%2B but from the "My Projects" list of
projects I can't click on "Qpid C++" because the link isn't escaped.
Before I dive into the source and see, is there a reason this can't
work?

Thanks,

-Steve

> -----Original Message-----
> From: Bill Hoffman [mailto:bill.hoff...@kitware.com] 
> Sent: Wednesday, June 10, 2009 3:59 PM
> To: Steve Huston
> Cc: 'David Cole'; cmake@cmake.org
> Subject: Re: [CMake] Trouble starting ctest run with 
> intention of reportingto dashboard
> 
> 
> Steve Huston wrote:
> 
> > 
> > You should be able to now.
> > 
> 
> Yup.
> 
> Here is how you run it:
> 
> hoff...@corrin ~/Projects/qpid/qpid/cpp
> $ cat myscriptnew.cmake
> set (CTEST_SOURCE_DIRECTORY c:/hoffman/Projects/qpid/qpid/cpp)
> set (CTEST_BINARY_DIRECTORY c:/hoffman/Projects/qpid/qpid/cpp/rhel5)
> SET(CTEST_CMAKE_GENERATOR "Unix Makefiles")
> SET(CTEST_BUILD_COMMAND make)
> set(CTEST_SITE "Kitware")
> CTEST_START("Experimental")
> CTEST_CONFIGURE(BUILD "${CTEST_BINARY_DIRECTORY}")
> CTEST_BUILD(BUILD "${CTEST_BINARY_DIRECTORY}")
> CTEST_TEST(BUILD "${CTEST_BINARY_DIRECTORY}")
> CTEST_SUBMIT()
> 
> hoff...@corrin ~/Projects/qpid/qpid/cpp
> $ /cygdrive/c/Program\ Files/CMake\ 2.6/bin/ctest.exe -S 
> myscriptnew.cmake -VV
> 
> And here is the build:
> http://www.riverace.com/CDash-1.4.2/viewConfigure.php?buildid=17
> 
> 
> -Bill
> 

_______________________________________________
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 CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Reply via email to