OrgACRN
/
sof
mirror of https://github.com/thesofproject/sof.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
sof/versions.json

8 lines
73 B
JSON
Raw Normal View History

version.cmake: switch SOF_MAJOR etc. to a new, static `versions.json` As discussed in #6952, relying on `git describe` for defining SOF_MAJOR and friends is very brittle and unreliable. Switch to a static versions.json file instead. Note the full `git describe --tags` output is _still_ present in the binary, this is useful and left unchanged. It's just not used any more to guess SOF_MAJOR, SOF_MINOR and SOF_MICRO. Use JSON because CMake and pretty much every other piece of software has a JSON parser out of the box. This aligns with linux/Makefile, Zephyr/VERSIONS and probably many others. - except we use JSON because we're in 2023 so we don't spend time having fun re-implementing parsers any more. Signed-off-by: Marc Herbert <marc.herbert@intel.com>
2023-04-28 07:19:05 +08:00
{
"SOF": {
"MAJOR": "2",
versions.json: version to 2.7.99 With stable-v2.7 branch create, set the mainline version to 2.7.99 to prepare for SOF v2.8 development. Signed-off-by: Kai Vehmanen <kai.vehmanen@linux.intel.com>
2023-09-01 17:14:51 +08:00
"MINOR": "7",
versions.json: bump to 2.6.99 Adopt Zephyr's (and others) .99 convention to indicate a development branch. Signed-off-by: Marc Herbert <marc.herbert@intel.com>
2023-06-03 04:11:22 +08:00
"MICRO": "99"
version.cmake: switch SOF_MAJOR etc. to a new, static `versions.json` As discussed in #6952, relying on `git describe` for defining SOF_MAJOR and friends is very brittle and unreliable. Switch to a static versions.json file instead. Note the full `git describe --tags` output is _still_ present in the binary, this is useful and left unchanged. It's just not used any more to guess SOF_MAJOR, SOF_MINOR and SOF_MICRO. Use JSON because CMake and pretty much every other piece of software has a JSON parser out of the box. This aligns with linux/Makefile, Zephyr/VERSIONS and probably many others. - except we use JSON because we're in 2023 so we don't spend time having fun re-implementing parsers any more. Signed-off-by: Marc Herbert <marc.herbert@intel.com>
2023-04-28 07:19:05 +08:00
}
}