MantisBT - CMake
View Issue Details
0010396CMakeCMakepublic2010-03-09 14:522011-05-02 14:46
Sebastian Herbst 
David Cole 
normalfeaturealways
closedwon't fix 
CMake-2-8 
CMake 2.8.4 
0010396: Support for solution name change
I added a CMake variable (CMAKE_SOLUTION_NAME) to choose another name for the
generated visual studio solution file. This is very neat if you have multiple
differently configured of the same solution open at the same time and
want to quickly know which configuration working on.
No tags attached.
patch 0001-solution-name-can-now-be-set-CMAKE_SOLUTION_NAME.patch (1,910) 2010-03-09 14:52
https://public.kitware.com/Bug/file/2945/0001-solution-name-can-now-be-set-CMAKE_SOLUTION_NAME.patch
Issue History
2010-03-09 14:52Sebastian HerbstNew Issue
2010-03-09 14:52Sebastian HerbstFile Added: 0001-solution-name-can-now-be-set-CMAKE_SOLUTION_NAME.patch
2011-01-17 15:06David ColeAssigned To => David Cole
2011-01-17 15:06David ColeStatusnew => assigned
2011-01-17 15:09David ColeNote Added: 0024800
2011-01-17 15:09David ColeStatusassigned => resolved
2011-01-17 15:09David ColeFixed in Version => CMake 2.8.4
2011-01-17 15:09David ColeResolutionopen => won't fix
2011-05-02 14:46David ColeNote Added: 0026349
2011-05-02 14:46David ColeStatusresolved => closed

Notes
(0024800)
David Cole   
2011-01-17 15:09   
I don't think allowing rename of the generated solution file is a good idea for CMake in the general case.

CMake has always used the "project(" command's name as the name of the solution file and there are other tools that depend on that assumption to generate correct build commands using that solution file name. (So, in other words, there's more to it than just the simple attached patch.)

I'm reluctant to change this behavior anyway, even if the patch were complete, for all of cmake, ctest and cpack, because there may be external tools that also depend on the predictability of the generated solution name remaining constant.

Feel free to re-open this issue for further discussion if you think this decision is incorrect.

Thanks.
(0026349)
David Cole   
2011-05-02 14:46   
Closing resolved issues that have not been updated in more than 3 months.