On Saturday 02 February 2008, Matthew Woehlke wrote: > Ick. Please, no http://www.cygwin.com/acronyms#TOFU. > > James Bigler wrote: > > Matthew Woehlke wrote: > >> but I couldn't figure out how to tell the script what parameters it > >> should run with. > > > > [snip] > > Make sure you put the arguments before theh -P ${my_cmake_script} or the > > arguments won't get passed in. > > Ah, so *that's* what I was doing wrong. Sigh. It would be really nice if > 'man cmake' documented that (in fact, if it just plain documented that > yes, you /can/ pass defines into a -P script). > > Maybe like this? > > SYNOPSIS > cmake [options] <path-to-source> > cmake [options] <path-to-existing-build> > cmake [options] -P <file> > cmake -E [command] > > -P <file> > Process script mode. > > Process the given cmake file as a script written in the CMake > language. No configure or generate step is performed and the cache is > not modified. Arguments may be passed to the script as CMake variables > by using -D. -P should be the last option on the command line.
I think this is documented now in cmake 2.4.8 Alex _______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
