On Tue, Feb 3, 2009 at 3:46 PM, Jean-Sébastien Guay <
jean-sebastien.g...@cm-labs.com> wrote:

> Hi Robert,
>
> I just added a nightly build scheduled task on my machine, and ran it a few
> times to see how it ran. You can see WHITESTAR is me. (incidentally, I
> changed my site name to WHITESTAR_jean-sebastien_guay at one time, but
> didn't change it the next time - anyone know how to remove an unused entry
> in the CDash page? :-) )
>
> It seems to me that using /build will not really be useful to track
> warnings, since only changed .cpp files and files that depend on changed
> headers will be recompiled each time, so getting 0 warnings doesn't mean
> there are 0 warnings in the whole build, just in the subset of files
> compiled.
>
> I tried using /rebuild, but that seems to only rebuild the CMake
> configuration, not the individual projects (the
> WHITESTAR_jean-sebastien_guay build was done with /rebuild, and you can see
> that only one file was compiled if you look at the build log). So using
>
>    devenv OpenSceneGraph.sln /rebuild Release /project Nightly
>
> doesn't seem to work as expected. I used /build and instead deleted my
> build directory's contents in order to rebuild everything. Perhaps I'm doing
> something wrong.


In your CTest script set the following command:

SET(CTEST_START_WITH_EMPTY_BINARY_DIRECTORY TRUE)


Also, another useful tip is to add the "-A" flag to the command used to run
CTest.  This will cause your CTest script to be visible on the public
dashboard.

SET (CTEST_COMMAND
  "\"/wherever/bin/ctest\" -D Nightly -A
\"${CTEST_SCRIPT_DIRECTORY}/${CTEST_SCRIPT_NAME}\""
  )


The CMake dashboard is also a treasure-trove of information regarding how to
setup a CTest script:
http://www.cdash.org/CDash/index.php?project=CMake


-- 
Philip Lowman
_______________________________________________
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to