MantisBT - CMake
View Issue Details
0012623CMakeCTestpublic2011-12-13 06:492016-06-10 14:31
doob 
Kitware Robot 
normalminoralways
closedmoved 
x86_64Windows7
CMake 2.8.6 
 
0012623: ctest_build() with Visual Studio 2008 Generator calling wrong Solution name.
If configured to build a Visual Studio 2008 Solution the ctest_build() command fails if the executable target name of the project doesn't match the projects name set by the project() cmake command.

CTest calls:
VCExpress.exe ${Targetname}.sln /build Release /project ALL_BUILD

instead of
VCExpress.exe ${Projectname}.sln /build Release /project ALL_BUILD

However the name of the solution that must be given on the commandline is set to the name given by project() in CMakeLists.txt, so calling VisualStudio with the name of the target is a bug.

No tags attached.
Issue History
2011-12-13 06:49doobNew Issue
2011-12-15 05:43doobNote Added: 0027982
2012-08-11 21:09David ColeStatusnew => backlog
2012-08-11 21:09David ColeNote Added: 0030337
2016-06-10 14:28Kitware RobotNote Added: 0041945
2016-06-10 14:28Kitware RobotStatusbacklog => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:28Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0027982)
doob   
2011-12-15 05:43   
There is a little mistake in the originally report. Acutally ctest_build() uses the name configured as the project name for the dashboard in CTestConfig.cmake as the solution name when calling VisualStudio instead of the solution name configured by the project() command in the CMakeLists.txt of the project.

I.e. ctest confuses CMAKE_PROJECT_NAME with CTEST_PROJECT_NAME.


CTest calls:
VCExpress.exe ${CTEST_PROJECT_NAME}.sln /build Release /project ALL_BUILD

instead of
VCExpress.exe ${CMAKE_PROJECT_NAME}.sln /build Release /project ALL_BUILD
(0030337)
David Cole   
2012-08-11 21:09   
Sending old, never assigned issues to the backlog.

(The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...)

If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^]

It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.
(0041945)
Kitware Robot   
2016-06-10 14:28   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.