commit | 4902470528ac39416028fb66b2cdb3c6e4ad55db | [log] [tgz] |
---|---|---|
author | Chris Forbes <chrisforbes@google.com> | Thu Sep 26 16:04:05 2024 +1200 |
committer | Chris Forbes <chrisforbes@google.com> | Thu Sep 26 16:04:05 2024 +1200 |
tree | 3f1e07f478710653c0a5d12aec4cdd05bef0e8ee | |
parent | 91c13c88acab7c442feec1efb953aa57de6fcf49 [diff] |
Move some copy_and_blit tests to the 2024 testlist These tests are causing issues with some pre-2024 GRF drivers. Bug: b/362911337 Ignore-Khronos-First: Android-specific testlist maintenance Change-Id: Ib4cd54fe51847fa92399312ccb9115aedd858224
This repository contains Khronos Conformance Testing Suite called VK-GL-CTS which originated from dEQP (drawElements Quality Program). VK-GL-CTS contains tests for several graphics APIs, including OpenGL, OpenGL ES, EGL, Vulkan, and Vulkan SC.
Up-to-date documentation for VK-GL-CTS is available at:
The .qpa logs generated by the conformance tests may contain embedded PNG images of the results. These can be viewed with scripts/qpa_image_viewer.html
, by opening the file with a web browser and following its instructions, or using the Cherry tool.
This repository includes Khronos Vulkan CTS under external/vulkancts
directory. For more information see Vulkan CTS README.
This repository includes Khronos OpenGL / OpenGL ES CTS under external/openglcts
directory. For more information see OpenGL / OpenGL ES CTS README.
When configuring the source code of VK-GL-CTS for running either Vulkan Conformance Tests or OpenGL(ES) Conformance Tests as described above, CMake will generate build files that, by default on desktop platforms, will build every possible project binary. This may be undesirable due the amount of time and disk space needed to perform the build.
One way of selecting only a subset of the targets to be built is using CMake's target selection mechanism. For example, the following command will only build deqp-vk
, the main Vulkan Conformance Tests binary:
cmake --build BUILD_DIRECTORY --target deqp-vk
When building only a subset of targets is the preferred default behavior for a given working copy or build directory, there's a second target selection mechanism that can be used to avoid passing the --target
option every time: the SELECTED_BUILD_TARGETS
CMake option. If set to a non-empty value, only the targets listed in that configuration option, separated by spaces, will be built.
For example, passing -DSELECTED_BUILD_TARGETS="deqp-vk deqp-vksc"
when configuring the project will make cmake --build BUILD_DIRECTORY
act as if it had been passed --target deqp-vk --target deqp-vksc
as additional arguments.
IMPORTANT: Target subset selection may not have been thoroughly tested in all enviroments and situations, and it does not replace the instructions given for the purposes of creating a conformance submission.
ANGLE can be built for Android by following the instructions here.
The resulting ANGLE shared object libraries can be linked against and embedded into dEQP.apk
with the --angle-path
option. This will cause dEQP.apk
to use the ANGLE libraries for OpenGL ES calls, rather than the native drivers.
An ABI must be specified and the directory structure containing the ANGLE shared objects must match it so the build system can find the correct *.so
files.
Assuming ANGLE shared objects are generated into ~/chromium/src/out/Release/
and dEQP.apk
will be generated with --abis arm64-v8a
, issue the following commands:
cd ~/chromium/src/out/Release/ mkdir arm64-v8a && cd arm64-v8a cp ../lib*_angle.so .
The --angle-path ~/chromium/src/out/Release/
option can then be used to link against and embed the ANGLE shared object files. The full command would be:
python scripts/android/build_apk.py --sdk <path to Android SDK> --ndk <path to Android NDK> --abis arm64-v8a --angle-path ~/chromium/src/out/Release/