I am using MDK 5.17 but the problem I am having also exists in previous versions.
I have a very large project (1000s of files) with 28 variants/targets. Whenever I save the project file or exit uVision it takes 1-2 minutes to save, "Not Responding" appears but it does eventually respond once the save is complete.
The .uvprojx file is 6M and the .uvoptx is 2M.
Usually if I know I am not going to change the project file then I write-protect the .uvprojx and .uvoptx files and the problem no longer occurs when exiting uVision.
Anyone else have this problem? Any suggestions on how to solve it, without splitting my project up ?
I have viewed the contents of the project file in an editor and there seems to be lots of duplication - it all looks very inefficient.
"It would be useful if uVision provided a way to exit without saving the Project!"
Most definitely so. I manage by having the project in a source code repository and verify the diff and potentially restore a previous version.
But for a person that doesn't have a copy in the repository, they would have to quickly move to the project filer and make a copy of the project file before exiting, in case they know they have been doing some experiment they don't dare to save.
Agreed, but my main complaint is the length of time it takes to save, and the amount of duplication in the project file.
Duplication is irrelevant. 6MB of disk space is irrelevant. The issue here is that it sounds like there might be some O(N^2) code with regards to the file size.