See http://www.keil.com/forum/56892/
"The project file should have been 100% focused on the rules required to perform the similar task of a Makefile. Everything else should have been optional information stored in separate files that doesn't need to be version-controlled and that can be auto-created if missing"
I entirely agree. It seems that Keil have totally broken the Project File arrangement as far as Version control goes.
:-(
And how is it intended that the Pack status should be controlled??
" ... about this critical part of how to use the Keil tools. And if you do get into troubles writing that whitepaper, then that would indicate that there might be issues with the separation of information in the different uVision project files."
Absolutely!
Then you might see things like the fact that the filetype descriptions are wrong; eg:
http://www.keil.com/support/man/docs/uv4/uv4_b_filetypes.htm
"*.UVOPTX: µVision5 project options. Contains the settings for the debugger, trace configuration, breakpoints, currently open files, ... . This mandatory XML file can be shared in a work-group."
Actually, it does not contain anything about "currently open files" - that's in the project.uvguix.<user> "user preferences" file.
However, it does show which groups in the Project explorer are expanded or collapsed - which are, surely, "user preferences" and should **not** be in a shared workgroup file!?!?
And Breakpoints should, surely, **not** be in a shared workgroup file!?!?