Part Number: C2000WARE
Hi
We are using the C2000ware SDK in our projects, this is good and bad.
The major bad part is that it is not controlled by a versioning system, just floating around on different developers hard disks.
I did made some setup scripting for our projects to ensure the correct version of the C200Ware package is installed.
But this only tells you that the package was installed. Not if there has been changes to the files in that installation.
I recently had a case of "it works on my PC" where it turned out I accidentally edited the device.h file inside the C2000Ware folder, and thus that change was not part of my next git commit.
And yes in the current shape of CCS this mistake is easily made!
I am considering either
- Setting up some hash calculation check of the C2000Ware install to run on each build, issuing warnings if there is a mismatch.
Or
- Putting the C2000Ware inside a git repo, and let is be controlled that way.
Regarding 1. Any recomendations how to integrate that in CCS, also so I am sure it runs the hash on the C200Ware folder actually used, Or other reccomandation/experiences on that approach (including "tried that don't do it")
Regarding 2. Besides the immense hassle to add new versions of C2000ware to a git repo and maintaining that.
How do I ensure that CCS is using the folder provided by git, and not some random folder from that user installing C2000ware in other contexts. and I am not talking malicious users here, so a "not to oversee" warning is still fine. As far as I can tell the search folders for ti-products is defined by the workspace and not the project.
Regarding hassle putting it in git, the download restrictions that you put on the C2000Ware download makes it close to impossible to script this step. And scripting it is the best way to ensure this procedure does not break, just because I am assigned to a new project. ( I am sure you know the Agile concept of Automate, Automate, Automate)
