2009/7/2 Marcel Loose <[email protected]>: > Hi Eric, >> The variable your are testing may contain "un-evaluated" var >> or some special regex character( *, ?, ...) >> >> See attached example, you may test it with >> $ cmake -P matches.cmake >> MATCHES -- MYVAR = A good var >> Look that one = double-dollar = blah / single-dollar = MYVAR2 >> NO MATCHES ** MYVAR = MYVAR2 >> $ >> >> However I have no such usage currently :-) > > If I understand your script correctly, then the trick of this construct is to > check whether the variable MYVAR is defined in terms of one (or more) other > variables. Correct?
This is not the only NO MATCHES case, if the variable value contains special regex character you get NO MATCHES too. > If so, I still don't quite get the usage pattern in, e.g., > CheckIncludeFile.cmake. What are they trying to check? Better ask the author of this file :-) CVS commit on the file were done by king --> Brad King martink --> ?? hoffman --> Bill Hoffman andy --> ?? -- Erk Membre de l'April - « promouvoir et défendre le logiciel libre » - http://www.april.org _______________________________________________ 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
