Instead of adding a new series of option to the cmake tool, why not adding a convenient script generated based on the content of CMakeLists files that is called configure and follow the autoconf way of things. This can be a macro which is used when CPack is used or something like that.
On 8/9/07, Brandon Van Every <[EMAIL PROTECTED]> wrote: > On 8/8/07, Philip Lowman <[EMAIL PROTECTED]> wrote: > > > > I don't know where -DUSE_FOO or -D USE_FOO came from, it doesn't appear > > to be legal in 2.4.6. > > Oops. Guess I haven't done enough of these to remember how I did them. > > > The fact that people don't even know the proper way to define variables > > at the command line (myself included) should be proof positive that > > CMake could use some improvement when operating in command line mode. > > I don't think that follows. The format for -D is actually well > documented in cmake.html. Just because people don't do this a lot > with CMake, and don't know things off the top of their heads, doesn't > mean the method is wrong, broken, or needing improvement. > > I think this is purely a marketing issue. > > Anyways, people can feel free to put a feature request in the bug > tracker. I don't see any tremendous harm in allowing --enable-* style > commands. > > > Cheers, > Brandon Van Every > _______________________________________________ > CMake mailing list > CMake@cmake.org > http://www.cmake.org/mailman/listinfo/cmake > _______________________________________________ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
