MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0011048CMakeCMakepublic2010-07-27 14:432016-06-10 14:31
ReporterZack Galbreath 
Assigned ToKitware Robot 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product VersionCMake-2-8 
Target VersionFixed in Version 
Summary0011048: Better error message needed when CTEST_PROJECT_NAME does not match
DescriptionThis issue only affects Visual Studio builds, as they use CTEST_PROJECT_NAME to determine the name of the .sln file to load.

If the parameter passed to CTEST_PROJECT_NAME does not match the PROJECT() name in the corresponding CMakeLists.txt file it shows up on CDash as a build warning:

non-zero return value in ctest from: C:\PROGRA~1\MICROS~1.NET\Common7\IDE\devenv.com

This should be considered a build or configure error instead, with a more explicit message stating what's going wrong.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-07-27 14:43Zack GalbreathNew Issue
2010-12-15 11:12David ColeAssigned To => David Cole
2010-12-15 11:12David ColeStatusnew => assigned
2012-08-13 15:06David ColeStatusassigned => new
2012-08-13 15:06David ColeNote Added: 0030588
2012-08-13 15:07David ColeStatusnew => backlog
2012-08-13 15:21David ColeAssigned ToDavid Cole =>
2016-06-10 14:28Kitware RobotNote Added: 0041734
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
(0030588)
David Cole   
2012-08-13 15:06   
Sending old, not-recently-updated issues to the backlog.

(The age of the bug alone 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.
(0041734)
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.