CAPI2 is constantly getting new features. When these are getting used in core description files, they are not compatible with older versions of FuseSoC anymore as examplified in https://github.com/chipsalliance/Cores-SweRVolf/issues/32
We should look into better version managment. First idea that comes to mind is adding a minor version to the CAPI. Longer term it could be a good idea to split out the CAPI definition to its own project with validators and stuff
CAPI2 is constantly getting new features. When these are getting used in core description files, they are not compatible with older versions of FuseSoC anymore as examplified in https://github.com/chipsalliance/Cores-SweRVolf/issues/32
We should look into better version managment. First idea that comes to mind is adding a minor version to the CAPI. Longer term it could be a good idea to split out the CAPI definition to its own project with validators and stuff