On 2007-09-23 20:58-0700 Sanchez, Juan wrote:

Well the fundamental problem is the point when the test gets run.

When you run ctest (after cmake and make).

I would think your solution requires that the test has already been
executed.  For my purposes, that is way too premature and costly.

I believe you are concerned about an issue that does not exist.  Hopefully,
my answer above addresses your concern.

[...]The whole point of me querying
the list about this type of stuff is to share collective experiences about
an issue I don't believe to be covered in the online or book documentation.

We (PLplot) use ctest to extensively test our software build, and I am sure
the same is true of most other mature projects that use cmake.  I think you
are concerned it is something really complicated when in fact it is standard
stuff that is pretty trivial to set up. You set up ctest with ADD_TEST at
cmake time (look at the ADD_TEST documentation for more details), and the
actual test gets run when you run ctest (after build time).  (Run ctest
--help-full for more details).

It should all become clear once you run a simple ctest case following the
documentation I have specified.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__________________________

Linux-powered Science
__________________________
_______________________________________________
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Reply via email to