Compilation scripts on different distributions (i.e. arch, gentoo) rely
on the tarball name to use hyphens between words.
This patch will create tarballs with hyphenated names
TEST="make dist, should produce libva-utils.tar.*"
Fixes#21
Signed-off-by: Daniel Charles <daniel.charles@intel.com>
This is from make dist command. The EXTRA_DIST inside the Makefile.am
was mistakenly overridden and as such the tarball was missing the gtest
dependencies
TEST="./autogen --prefix=<some prefix>... //more options if needed"
TEST="make dist, resultant tarball should include the gtest subfolders"
TEST="compilation of the resultant tarball should be successful when"
TEST="adding --enable-tests to configure options"
Fixes#20
Reported-by: Focus Luo <focus.luo@intel.com>
Signed-off-by: Daniel Charles <daniel.charles@intel.com>
On the summary the driver folder doesn't need to be shown
as libva and intel-vaapi-driver are already exposing such
information
Fixes#15
Signed-off-by: Daniel Charles <daniel.charles@intel.com>
libva-utils contains utilities and example applications to
use VA-API.
--enable-tests configure flag enables a suite of unit tests
that are based on Google Test Framework
The flag name is modified to keep consistency with intel-vaapi-driver
unit tests configuration flag
Fixes:#12
Signed-off-by: Daniel Charles <daniel.charles@intel.com>
add a new test that will printout which profile/entrypoint
combinations will be skipped while running the suite.
Skipped tests are now recording a property and using test_streamable
to print profile/entrypoint without function calling.
Fixes#2
Signed-off-by: Daniel Charles <daniel.charles@intel.com>
The purpose of createsurfaces is to operate on supported
profile/entrypoint as reported by the driver. Other tests
handle the non-supported combinations and report properly.
There's no need to duplicate printing information about
skipped tests here
Fixes#1
Signed-off-by: Daniel Charles <daniel.charles@intel.com>
debian control files are maintained by packagers
Yes there is a "convenience" factor to roll your
own debian package, but this is not maintained by
us and represents a fork from debian packagers.
As with the bit rot of libva.spec, remove this.
fixes#6
Signed-off-by: Sean V Kelley <seanvk@posteo.de>
When gtest prints out test params (e.g. --gtest_list_tests)
for VAProfile and VAEntrypoint, it prints the value. This
makes it difficult to know which profile/entrypoint it
actually is without cross-referencing the va header manually.
This patch adds output stream operators for VAProfile and
VAEntrypoint to print out the name along with its value. GTest
will automatically use these operators to print profile/entrypoint
params in its test output.
Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
This initial set of files covers the va.h API for all the
functions used to exercise successfully the VA-API.
Tests are divided per VA-API function with a common Fixture that
contains all calling functions to the VA-API. For the use cases
covered already there are tests for the proper functionality and also
for expected error situations.
The tests creates combinations with all the inputs to the VA-API function
and then it checks the results based on what the driver implementation reports
as supported
The set of tests can be run on any h/w supported and any driver.
The VendorString test is assuming Intel i965 driver, please help
adding the test for other drivers
More tests will be continously added
Signed-off-by: Daniel Charles <daniel.charles@intel.com>
Add test main() definition.
Also provide a test.h header with common test includes and
definitions that can be included by all test compilation
units.
taken from libva-intel-driver and properly adapted to libva-utils
Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
Reviewed-by: Sean V Kelley <seanvk@posteo.de>
Signed-off-by: Daniel Charles <daniel.charles@intel.com>
Define autoconf/automake rules to build libgtest.la
as a convenience library.
Add --enable-gtests configure option (default:no).
All Gtests are built by configure flag, since this is a test
repository then the differentiation is made.
Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
Reviewed-by: Sean V Kelley <seanvk@posteo.de>
Signed-off-by: Daniel Charles <daniel.charles@intel.com>
We will use the Google Test Framework for testing.
Google Test is not meant to be packaged and used as a system
dependency like other libraries. Google Test recommends that
it be custom compiled for each project that uses it. Thus,
we'll keep our own copy of it here and compile it as needed.
Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
Reviewed-by: Sean V Kelley <seanvk@posteo.de>
libva-utils is a new git repository that will host sample applications
for libva, conformance tests and others relevant to libva
It is using the same version as libva and it should follow libva version.
It is intended to be released together with libva
It has the same license as libva
Initial functionality ports the vainfo application from libva repository.
The git history for it will remain on libva. To port vainfo, also the
a common libva-display library was ported. The original tests for encoder
and decoder are also ported to this repository. debian folder for vainfo
was also ported
The basic tests are going to be substituted by a new set of tests based
on Gtest framework.
libva-utils will dynamically link libva, use pkg-config to compile and
link properly.
Signed-off-by: Daniel Charles <daniel.charles@intel.com>
Nicolas Chauvet