| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Meson allows to use absolute paths for libdir and includedir [0]. But if
they're absolute paths one must not append the prefix. The join_paths()
function [1] nicely supports both relative and absolute paths.
This is e.g. important for Nixpkgs (i.e. Nix(OS)) where binaries and
library files are usually installed under different prefixes.
[0]: https://github.com/mesonbuild/meson/commit/a513bcfde613f2a0403f7b0cd34d4bd62674c1d8
[1]: https://mesonbuild.com/Reference-manual.html#join_paths
Signed-off-by: Michael Weiss <dev.primeos@gmail.com>
|
| |
|
|
| |
Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
|
| |
|
|
|
|
| |
Fixes: #134
Signed-off-by: Víctor Manuel Jáquez Leal <vjaquez@igalia.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The APIs/data structures defined in va_tpi.h and va_egl.h are used
to implement buffer sharing between libva and the 3rd party libraries.
We have an official buffer sharing machnism in VA core, so libva-tpi and
libva-egl are unnecessary any more.
However va_egl.h or va_tpi.h is included uselessly in a few places,
e.g. https://github.com/01org/libyami/blob/apache/vaapi/vaapidisplay.h#L22
So va_egl.h and va_tpi.h are kept with a deprecation warning message.
Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>
|
| |
|
|
|
|
| |
Fixes #95
Signed-off-by: Lim Siew Hoon <siew.hoon.lim@intel.com>
|
| |
|
|
| |
Signed-off-by: Gwenole Beauchesne <gwenole.beauchesne@intel.com>
|
| |
|
|
|
|
|
|
| |
In this case, VA/GLX API is disabled and another backend shall be
built instead.
Signed-off-by: Dmitry Ermilov <dmitry.ermilov@intel.com>
Signed-off-by: Gwenole Beauchesne <gwenole.beauchesne@intel.com>
|
| |
|
|
|
|
|
|
| |
This API makes it possible to use DRM-based VA drivers without an X server.
Since this is a renderless API, vaPutSurface() is not available.
Signed-off-by: Dmitry Ermilov <dmitry.ermilov@intel.com>
Signed-off-by: Gwenole Beauchesne <gwenole.beauchesne@intel.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We have to consider three distinct versions at this time: the VA-API
version, the library package version number, and the DSO version.
* VA-API version:
- increment major for any ABI change (which shall not occur!)
- increment minor for any interface change (e.g. new or modified function)
- increment micro for any other change (e.g. new flag, new codec definitions)
- reset micro version to zero when minor version is incremented
- reset minor version to zero when major version is incremented
* libva package version number:
- major version is automatically generated from VA-API major version
- minor version is automatically generated from VA-API minor version
- increment micro for any library release
- reset micro version to zero when VA-API major or minor version is incremented
* DSO version:
The SONAME shall remain to libva.so.1 for VA-API 0.x.y as long as the ABI
is not changed. Thus, the library name is generated as libva.<x>.<y>.0 where
<x> = VA-API major version + 1
<y> = 100 * VA-API minor version + VA-API micro version
For example:
VA-API 0.32.0 generates libva.so.1.3200.0 (libva 1.0.14 as of today)
VA-API 0.34.1 generates libva.so.1.3401.0 (e.g. libva 1.2.1)
VA-API 1.2.13 generates libva.so.2.213.0 (e.g. libva 2.2.13)
Signed-off-by: Gwenole Beauchesne <gwenole.beauchesne@intel.com>
|
| |
|
