commit | fbb17203aee1ff3f32a04a5f83e427245457890f | [log] [tgz] |
---|---|---|
author | Timo Gurr <timo.gurr@gmail.com> | Tue Nov 06 16:17:27 2018 +0100 |
committer | U. Artie Eoff <ullysses.a.eoff@intel.com> | Tue Jun 04 08:46:38 2019 -0700 |
tree | 6e7f67aa684ff02d3c868bf434b39e157d6c5156 | |
parent | bf00cf2fef47c6a90eb5eef9ea3cb12cae5e1b3c [diff] |
meson: rename the h264enc binary to be in line with the autotools build h264enc collides with the h264enc binary installed by openh264 and the autotools based build names the binary h264encode.
#Libva-utils Project
libva-utils is a collection of utilities and examples to exercise VA-API in accordance with the libva project. --enable-tests (default = no) provides a suite of unit-tests based on Google Test Framework. A driver implementation is necessary to properly operate.
VA-API is an open-source library and API specification, which provides access to graphics hardware acceleration capabilities for video processing. It consists of a main library and driver-specific acceleration backends for each supported hardware vendor.
If you would like to contribute to libva, check our Contributing guide.
We also recommend taking a look at the ‘janitorial’ bugs in our list of open issues as these bugs can be solved without an extensive knowledge of libva-utils.
We would love to help you start contributing!
The libva-utils development team can be reached via our mailing list and on IRC in channel ##intel-media on Freenode.
We also use #Slack and host VAAPI Media Slack Team. You can signup by submitting your email address to our Slack Team invite page.
Slack complements our other means of communication. Pick the one that works best for you!