Draft: API: bump ABI version due to previous backwards-incompatible changes

Jan Erequested to merge
jeeb-/SVT-AV1:add_api_version into master

Description

Issue

Ever since 988e930c , API clients are effectively broken since there is no way of checking if one is building against a more recent or less recent version of SVT-AV1, while the number of arguments for svt_av1_enc_init_handle were changed in an incompatible manner.

The short-term fix-up is probably to utilize this existing version define, but the fact that at least according to its documentation, this define is supposed to reset at major bumps makes it much less usable as a simple "API version" which keeps on incrementing unrelated to the general software version. In other words, currently you always must add an additional check for the current major version, while also checking for this ABI version number. Thus, I am raising this MR in order to see the response for it.

Author(s)

@jeeb-

Performance impact

  • quality
  • memory
  • speed
  • 8 bit
  • 10 bit
  • N/A

Test set

  • obj-1-fast can be found here
  • other
  • N/A

Merge method

  • Allow the maintainer to modify and merge when PR is ready to create as many atomic commits as the change set requires. The maintainer will be able to fix typos / combine commit messages to create a more readable result.
  • I will clean up my commits and the maintainer shall use 'rebase and merge' to the master branch

(either is fine)

Merge request reports