tag | 0d95beecf11ae9513fc8055a2bd01dcdb81e841e | |
---|---|---|
tagger | Lorenzo Dal Col <lorenzo@khronosgroup.org> | Fri Nov 08 16:26:26 2024 +0100 |
object | 2559085d016a9ebcc343e7a21b64290ef19b708c |
Vulkan CTS 1.4.0.1 Fixes: * Fix clearing image with wrong subresource range * Add depth clamp range to pipeline construction util * Add missing pipeline barrier after dispatch in push descriptor tests * Set missing blend equation in extended_dynamic_state tests * Avoid comparing garbage memory in descriptor buffer capture-replay tests * Set missing depth clamp range in extended dynamic state tests * Add missing pipeline barrier after dispatch in cooperative matrix tests * Add missing pipeline barrier after dispatch in robustness tests * Add check result for SetForeground. * Add missing pipeline barrier after dispatch in descriptor limits tests * Fix sparse tests to handle planar DS aspects * Use exactly representable numbers for atomic 16f * Reduce iteration count in surface/swapchain maintenance1 tests again * Check timestampComputeAndGraphics * Add missing pipeline barrier after dispatch in zero_initialize_workgroup_memory tests * Add missing barrier in swapchain maintenance tests * Add missing pipeline barrier after dispatch in expect/assume tests * Check R64 format qualifier for storage images in robustness tests. * Fix the scratch size in acceleration structures update tests * Enable missing extension in swapchain simulate oom tests * Increase tolerance for chroma channel results * Fix dstStageMask in sync none_set_reset tests * Fixing the VkRayTracingShaderGroupTypeKHR in ray query tests * Fix VK_ANDROID_external_format_resolve input_attachment cases * Fix wrong bufferMemoryBarrierCount in pipeline barrier for some buffer_view tests * Fix synchronization issue in OpacityMicromapTests * Fix checking mesh shader support in shader object tests * Fix VK_API_MAX_FRAMEWORK_VERSION Others: * Update Vulkan 1.4 headers to the latest version
commit | 2559085d016a9ebcc343e7a21b64290ef19b708c | [log] [tgz] |
---|---|---|
author | Lorenzo Dal Col <lorenzo@khronosgroup.org> | Wed Nov 06 16:35:46 2024 +0100 |
committer | Lorenzo Dal Col <lorenzo@khronosgroup.org> | Wed Nov 06 16:35:46 2024 +0100 |
tree | c57b3c6138ee91bb9cf62ba89cdfe5b4196491c0 | |
parent | 3732007c7650cd88e3ce8d6312b0172160cb92d7 [diff] |
Fix VK_API_MAX_FRAMEWORK_VERSION Change-Id: Ib8f99b9c43797d403eb5f65941f9d7ba66e24cf6
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/