libva
libva copied to clipboard
meson: automatically correlated project version and api version number
In configure.ac we have project version correlated with api version in automated way. This was not done for meson and we start to see project support issues on this regard. Let's try to automate that and avoid these issues in the future.
Signed-off-by: Dmitry Rogozhkin [email protected]
yes, api version is base, libva is implementation of vaapi definition please refer https://github.com/intel/libva/blob/master/configure.ac#L65
Let me try. I am not expert in meson and not sure whether it will accept variable in the project()
statement declaration. But I might be just frightened by cmake. So, I'll try...
@XinfengZhang. @onabiull : this won't work(. Unfortunately meson requires project()
to be the very first statement. It does not accept variable declarations before it. Error is:
ERROR: First statement must be a call to project
So, if we want some automated correlation for meson between package and api versions we need to play from package version for meson. I.e. this PR as it stands now. Do we want that?
For meson the project version is a first class element for compilation and distribution. API version is specific to libva.