Other Parts Discussed in Thread: SYSCONFIG,
Hi
I am using the C200Ware SDK, especially the sysconfig part.
Out of necessity I have added some patches to the C2000Ware code, usually after some feedback in these forums.
As I am developing for a product, and not just my little one-off project, I need to keep track of versions, including the C2000ware library, to ensure our build system always uses the correct one.
So i end up having a version of <TI-release> + x Patches.
I also expect us to continue using and thus upgrading to newer versions of c200Ware, So i do not want to do a clone and own of the TI Release, also I don't want to keep reinventing the deep plate.
So I was considering if I could utilize the fact that TI has 4 digits in the version, the latest being 4.1.0.0. Looking back in the release history, most updates affects the second digit (semantic versioning would name this the minor). But there is a single exception to this
- 2.00.00.03 (29 Sep 2019)
- 2.00.00.02 (28 May 2019)
There seems to be no V 2.0.0.0?
Avery other release has only affected higher level numbers.
So my question is, could I reasonably assume that the last digit will be untouched by TI on future releases, and thus use it for my own patch level versioning.
The reason for me to reuse this version number is to utilize the check that is then already build into CCS, so it will complaint if it cannot find the correct version as specified by the project file. removing the task of adding another check to my build setup for checking the patch number. And also give future developers a better error message inside CCS.
