[CMake-Promote] a ./configure shell script stub

Brandon J. Van Every bvanevery at gmail.com
Sun May 28 19:43:24 EDT 2006


William A. Hoffman wrote:
>
> OK, sure, but that is not really my point.  The point is there maybe a handful of
> standard options that we could do, but what people will really want is the options
> that are specific to the project.   
True.  When I use ./configure, I use --prefix, --help, 
architecture-specific optimization flags, and project-specific options.  
That's about it.

> That is where it gets hard, because cmake has to be
> run before you can figure out what the options are.   That is why I suggested creating
> an options file.  It is not perfect because it could get out of date with the true
> options for the project.   But, it would give people a way to document a project and
> have a better command line.
>
> cmake --help ../path/to/source
> This would read CMakeCommandLineOptions.cmake, and print out the options found in the
> file.
>   

What is the motive for making it separate from CMakeLists.txt?


Cheers,
Brandon Van Every

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://public.kitware.com/pipermail/cmake-promote/attachments/20060528/df340538/attachment.htm


More information about the CMake-Promote mailing list