[CMake] "How To" Question

Richard Wackerbarth richard at nfsnet.org
Tue May 13 16:00:16 EDT 2008


I'm still trying to figure out how to handle the following two  
situations (simplified):

When we run the tests for our Nightly Dashboard, in addition to a  
number of other tests, consider "Test A" and "Test B".

If "Test A" fails, then I don't even want to attempt to run "Test B".




The program is a complex one that can run on a wide range of hardware.  
It can handle both "easy" data sets and "hard" ones. The "hard" ones  
push system resources, in terms of both cpu cycles and memory, and  
exercise parts of the program that are not necessary for the "easy"  
data sets.

Although it would try, we know, in advance, that some of the older  
hardware is not "capable" in handling the more difficult data sets.  
The test will fail, either because of memory or time constraints.

Therefore, I would like to avoid even attempting to run some of the  
tests on installations that have older CPUs or smaller memory.
Are there any standard CMake variables that can be tested to  
differentiate various machine capabilities? Is there any interest in  
establishing some?




More information about the CMake mailing list