View Issue Details [ Jump to Notes ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0012050CMakeCMakepublic2011-04-06 04:192016-06-10 14:31
ReporterGaleazzi 
Assigned ToKitware Robot 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionmoved 
PlatformPC x86OSWindows XPOS Version
Product VersionCMake 2.8.4 
Target VersionFixed in Version 
Summary0012050: missing file causes an empty solution
DescriptionWhen one (or more) file(s) listed in CMakeLists is not found the VS2008 solution becomes empty and it's not possible to recovery it anymore by VS2008.
Steps To Reproduce1 - Create a VS2008 solution based on a correct CMakeLists.txt
2 - Open the solution and edit CMakeLists.txt adding a non-existent file into the list of sources.
3 - Build the solution (F7 is my shortcut)
4 - It appears the message: << The solution 'name' has been modified outside the environment. Press Reload to load the update solution from disk.
Press Ignore to ignore the external changes. The changes will be used the next time you open the solution. >>
5 - If you press Reload, VS2008 will open a solution containing none projects, so it's not possible to recovery the situation. The only way is to fix the CMakeLists.txt by an external editor and generate the solution again by using cmake-gui or cmake command line.
TagsNo tags attached.
Attached Files

 Relationships

  Notes
(0026226)
James Bigler (developer)
2011-04-19 10:53

 I believe this is a problem, because missing files aren't detected until "Generation" time. By that time project files have started to be written, so when CMake encounters an error you end up with ungenerated files.

I agree it's an unfortunate problem that would be nice to be fixed.
(0026229)
Galeazzi (reporter)
2011-04-19 11:53
edited on: 2011-04-19 11:54

 A solution could be to write the project files with some temporany names and then rename them only if the generation phase doesn't fail.
(0030255)
David Cole (manager)
2012-08-11 11: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.
(0041828)
Kitware Robot (administrator)
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.

 Issue History
Date Modified Username Field Change
2011-04-06 04:19 Galeazzi New Issue
2011-04-19 10:53 James Bigler Note Added: 0026226
2011-04-19 11:53 Galeazzi Note Added: 0026229
2011-04-19 11:54 Galeazzi Note Edited: 0026229
2012-08-11 11:09 David Cole Status new => backlog
2012-08-11 11:09 David Cole Note Added: 0030255
2016-06-10 14:28 Kitware Robot Note Added: 0041828
2016-06-10 14:28 Kitware Robot Status backlog => resolved
2016-06-10 14:28 Kitware Robot Resolution open => moved
2016-06-10 14:28 Kitware Robot Assigned To => Kitware Robot
2016-06-10 14:31 Kitware Robot Status resolved => closed

Copyright © 2000 - 2018 MantisBT Team