As I see it, folks that are used to cmake/ccmake tend to want
cmake-gui
to work more like that. Whereas folks that are used to doing
everything
from GUI's and hardly if ever touch a command line want it to work
like
we're suggesting. Both points of view are IMO valid (though I tend
towards greater sympathy for the latter in this case).
(Personally, I'd say I'm middle of the road; I use a CLI plenty¹ -
and
TBH, ccmake much more than cmake-gui - but I (try to) understand and
respect the non-CLI use case.)
I would simply like to point out, with all due respect, that in the
non-CLI use case, it is IMPOSSIBLE to pass command line parameters.
Therefore, when discussing how command line parameters ought to behave,
you do not have to consider the non-CLI use case. (Other than,
obviously, not requiring any changes to the non-CLI use case to
accommodate new command line features...)
D
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
