3686049460
143: Deployment configuration r=kvark a=grovesNL Continue deployment configuration: - just run everything in `script` instead of separating them - only attempt to deploy for Rust stable builds - `skip_cleanup` forces temporary build artifacts not to be cleared and seems to be recommended for this deployment Co-authored-by: Joshua Groves <josh@joshgroves.com> |
||
|---|---|---|
| bench | ||
| conformance | ||
| etc | ||
| libportability | ||
| libportability-gfx | ||
| libportability-icd | ||
| modules | ||
| native | ||
| .gitignore | ||
| .gitmodules | ||
| .travis.yml | ||
| appveyor.yml | ||
| bors.toml | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CMakeLists.txt | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
gfx-portability
This is a prototype library implementing Vulkan Portability Initiative using gfx-hal. See gfx-rs meta issue for backend limitations and further details.
Showcase
Dota2:
RPCS3:
Dolphin:
Instructions
Despite the fact it's written in Rust, the produced binary is a standard dynamic library that can be linked to from any program (written in the language of your choice). Typically, you'd need to create a symbolic link with a name that a target application expects, e.g. libvulkan.dylib -> libportability.dylib.
Check out and build:
git clone --recursive https://github.com/gfx-rs/portability && cd portability
cargo build --manifest-path libportability/Cargo.toml --features <vulkan|dx12|metal>
Running Samples
LunarG (API-Samples)
After building portability as shown above, grab a copy from https://github.com/LunarG/VulkanSamples.
Manually override the VULKAN_LOADER variable and set it to the portability library.
set (VULKAN_LOADER "path/to/portability/library")
Then proceed with the normal build instructions.
Vulkan CTS coverage
Please visit our wiki for CTS hookup instructions. Once everything is set, you can generate the new results by calling make cts on Unix systems. When investigating a particular failure, it's handy to do make cts debug=<test_name>, which runs a single test under system debugger (gdb/lldb). For simply inspecting the log output, one can also do make cts pick=<test_name>.