Hi,
we recently switched from CCSv4.2.4 to CCSv5.1.0 and migrated some of our projects into a new workspace. Our projects are shared and managed with subversion version control system.
We have followed instructionsat slide 20 of the CCSv4 tips and tricks presentation to identify which CCS files must be checked in for the old CCSv4 projects:
http://processors.wiki.ti.com/images/0/09/CCSv4_Tips_%26_Tricks.pdf
Once the CCSv4 projects were set up correctly, the content of the project related files did not change even when switching to a different CCS active build configuration (e.g. from "debug" to "release").
For the new CCSv5 projects we added the additional .cproject file to version control, comparing to slide 83 of the CCSv5 advanced workshop:
Currently, we have the following issue:
When we change the active build configuration on a local project , both the .project and the .cproject files are touched. The .cproject file doesn't change structurally (although a couple of XML attributes swap places sometimes) and the .project file does change. We use pre-build steps to check for local modifications. That is a big problem since now we get conflicting changes in the version control system dependent on local active build configuration.
Steps to reproduce:
1. Change CCSv5 project active build configuration in workspace (e.g. from debug -> release).
2. You get chances in CCSv5 project files (.cproject, .project).
3. Another developer does the same or contrary thing concurrently.
4. You have conflicting changes in version control.
Does anybody have a suggestion?
Thanks,
Christian
