You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Personally I would suggest to create a tool to do that, so the only thing needs to do is to create a release tag, the cmsis_version.h will be generated automatically during compile time.
Not sure if I can create a pull request? If I can, I will be more than happy to make such auto generation script for a review. Thanks!
I appreciate that different versions can be misleading. We use independent versioning on multiple layers:
CMSIS Release Bundle, which is reflected by the tag
Software components in the bundle, e.g. this cmsis_version.h belongs to CMSIS-Core(M)
Versions and change dates of individual files, e.g. the specific cmsis_version.h
In the concrete case, CMSIS Release Bundle 5.6.0 contains CMSIS-Core(M) in version 5.3.0, and the cmsis_version.h file version is 5.0.3. Three different versions.
We played through a lot of variants on how to cope with versions on different layers. The solution we use since a while seems to be the only practical one.
I get code from https://github.com/ARM-software/CMSIS_5/releases/tag/5.6.0 , in which the source file cmsis_version.h includes bellow version code:
The file header also mismatch:
The text was updated successfully, but these errors were encountered: