- Mar 05, 2020
-
-
Ludovico de Nittis authored
With this helper we are able to test if VA-API is available and usable. It tests the ability to gather the supported configuration profiles, then it creates two surfaces and perform a few simple rendering transformations. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Feb 27, 2020
-
-
Ludovico de Nittis authored
With this helper we are able to test if VDPAU is available and usable. It is a simple test that renders a 4x4 surface and checks that the output is what we expected. Exit code is 0 on success. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Jan 09, 2020
-
-
Previously we were listing only ICDs (graphics drivers). With this commit we are now able to get a more complete vision of the running system listing also Mesa DRI and VA-API drivers. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Dec 05, 2019
-
-
Simon McVittie authored
Since steam-runtime-tools was made relocatable in c3a06cce, its build will fail with the Steam Runtime 1 'scout' version of dpkg if it is already installed system-wide. If the SDK container where steam-runtime-tools is built has our $(pkglibexecdir) populated with symbolic links to the dependency libraries, then dpkg-shlibdeps will look there to convert DT_NEEDED dependencies into Debian dependencies. Unfortunately, the version of dpkg in SteamRT 1 'scout' has Debian bug #843073, which means it assumes all libraries are found via their canonical names as listed in the dpkg database, not a symlink-based alias. This results in the build failing with an error similar to: dpkg-shlibdeps: error: no dependency information found for /usr/lib/x86_64-linux-gnu/steam-runtime-tools-0/libglib-2.0.so.0 (used by debian/libsteam-runtime-tools-0-helpers/usr/libexec/steam-runtime-tools-0/x86_64-linux-gnu-check-locale) Until we get a newer Docker image with a newer version of this package that works around this issue, we will have to remove it explicitly before running CI. Adding Build-Conflicts is not enough: autopkgtest installs build-dependencies, but does not remove Build-Conflicts. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Nov 11, 2019
-
-
Simon McVittie authored
They sometimes give different warnings. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Nov 08, 2019
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Oct 31, 2019
-
-
Simon McVittie authored
This avoids having to have precompiled SPIRV in the source tree. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Ludovico de Nittis authored
Some libraries like "libtheoraenc.so.1" or "libCgGL.so" assumes that you have already linked to other libraries. With this commit we add support for those situations with the concept of "hidden dependencies". Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Oct 29, 2019
-
-
Jeremy Whiting authored
%multiarch%-check-vulkan uses vulkan to draw a simple triangle in a 200x200 window (next commit will not draw the window) and reports any issues found. Exit code is 0 on success. shader.frag and shader.vert are shader source files compiled into shaders/frag.spv and shaders/vert.spv respectively by using glslc such as: glslc shader.frag -o shaders/frag.spv glslc shader.vert -o shaders/vert.spv Binary shaders included in commit because glslc hasn't been packaged for scout runtime yet. Also add libvulkan-dev and libxcb1-dev to ci dependencies.
-
- Sep 11, 2019
-
-
Simon McVittie authored
pressure-vessel will use these when it generates any missing locales. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Sep 09, 2019
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Aug 22, 2019
-
-
Simon McVittie authored
Using clang here isn't very important, but it might give us some extra compiler warnings that gcc wouldn't. ASan will detect memory leaks and other memory corruption, UBSan will detect other badness, and scan-build might give us some helpful warnings from static analysis. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Previously we used scout for all stages except build, which had the same practical effect, but this way round scales better if we want to run things like scan-build in a modern environment. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jul 26, 2019
-
-
Ludovico de Nittis authored
This helper takes a SONAME as an argument, and optionally a filename for symbols, and outputs a parsable JSON with the path, the dependencies and the possible missing symbols of the requested library. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Jul 24, 2019
-
-
Simon McVittie authored
We are targeting scout, but because scout is so old, its SDK environment is too old to run deb-build-snapshot. Instead, we do that step in a Debian 10 'buster' environment, and hand over the artifacts from that to the autopkgtest step. Our build-dependencies are not all preinstalled in the CI Docker images, so add them. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-