Skip to content

API functions for accessing version in runtime#443

Merged
fador merged 10 commits intoultravideo:masterfrom
agruzdev:api-version
Jan 20, 2026
Merged

API functions for accessing version in runtime#443
fador merged 10 commits intoultravideo:masterfrom
agruzdev:api-version

Conversation

@agruzdev
Copy link
Contributor

Added API functions for getting version string, version number, compiler name, and compilation date in runtime. It's useful when shared library is loaded in runtime.

@fador
Copy link
Member

fador commented Jan 20, 2026

Thanks, it would indeed be useful to get the info.
But you also need to add the definitions to the Autotools configure.ac since that's what we still officially support 😁

@agruzdev
Copy link
Contributor Author

Okay, I will do.
Just a bit confused. Why there is also API version 7.4.0 at the same time with project version 2.3.2 (used for releases)? The API version is used only for .SO files?

@fador
Copy link
Member

fador commented Jan 20, 2026

I would call it the legacy library versioning, with each change to the API we would increment the version. Major version increase would be a breaking API change and I don't think we had any of those.
Not sure does it matter anymore..

@fador fador added the safe to test Run tests on CI label Jan 20, 2026
@agruzdev
Copy link
Contributor Author

Done. I'm not experienced with autotools, but seems to work. All tests in AppVeyor are passed too.

@fador fador merged commit dc4a20e into ultravideo:master Jan 20, 2026
5 checks passed
@fador
Copy link
Member

fador commented Jan 20, 2026

Nice, thank you!
We are planning on deprecating the autotools at some point so I'm not so worried about that anyway ;)

@agruzdev agruzdev deleted the api-version branch January 20, 2026 13:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

safe to test Run tests on CI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants