On 14. Jan, 2010, at 14:44 , Eric Noulard wrote: > 2010/1/14 Michael Wild <[email protected]>: >> >> Exactly, and having simple "VCR-controls" to build and install (and perhaps >> clean) would be enough for those users. They don't want to look at the IDE >> or the source code, they just want to build and install. Heck, it would be >> enough for me in the most cases (I don't like IDE's, I'm a Vim person). As a >> nice feature one could add a menu-entry to run CPack to create a native >> installer. >> >> I think that cmake-gui could be the central place to drive simple >> configuration, build, packaging and installation from. For the fancy stuff >> the user will have to use the native generator (i.e. everything that can't >> be driven through cmake and cmake --build), but that's probably OK, these >> users won't mind. > > I like the idea and it seems reasonable however since cmake has two UI: > cmake-gui > ccmake > may be it's worth adding those feature to both UI ? > > I mean being able to download source run ccmake and end-up with a > installable package > (TGZ, RPM, DEB) etc... would be nice too. > > Todays you may do it with an extra "make package" after you run ccmake > not a big deal > but the UI may let you chose the type of [supported] installer package you > want.
Sure, but I suspect that most users using ccmake will be comfortable with typing "cmake --build ." and "cmake --build . --target install". (BTW, why doesn't the <dir> argument after --build default to CMAKE_BINARY_DIR???) Michael _______________________________________________ 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
