Safe and rich Rust wrapper around the Vulkan API
Go to file
Jim Blandy 01aaa2e524 Doc fixes (#1007)
* Use 'greater than' instead of 'superior to'.

Using 'X is superior to Y' to mean 'X > Y' is not standard mathematical usage. I
think I've seen 'superior to' used in lattice theory, but that's not relevant to
these cases.

* trait RenderPassDesc: Correctly describe when `None` is returned.

This seems to be an off-by-one error in the documentation. Looking at the
implementations generated in `src/framebuffer/macros.rs`, for example,
the various elements of each sequence are numbered from 0 to n-1.

* Typo: 'anistropic' -> 'anisotropic'.

* sampler::MipmapMode::Linear: Clarify description.

The docs seem to suggest that if the dimensions match a given level D, then
`Linear` would use levels D-1 and D+1, which is senseless. The new wording is
meant to be closer to the calculation described in Vulkan 1.1.82 §15.6.7.

* Typo: 'transitionned' -> 'transitioned', and similar.

* Doc fix: 'more optimal' -> 'more efficient'

Rationale for the curious:

'Optimal' is an absolute; once something is optimal, it cannot be made more so.
Absolutes can be weakened, as in 'almost optimal', but not strengthened, as in
'more optimal' or 'very optimal'. 'Efficient' is not an absolute: one thing
might be 'more efficient' than another.

* Minor doc fixes.

* Doc fix: 'performances' -> 'performance' throughout.
2018-08-10 14:51:26 +02:00
examples Upgrade dependencies (#1012) 2018-08-10 14:50:38 +02:00
glsl-to-spirv Update glslangValidator.exe to latest version (#979) 2018-06-30 19:18:37 +02:00
vk-sys IOS and MacOS Surface ids were not to spec (#998) 2018-07-28 15:16:57 +02:00
vulkano Doc fixes (#1007) 2018-08-10 14:51:26 +02:00
vulkano-shader-derive Update glslangValidator.exe to latest version (#979) 2018-06-30 19:18:37 +02:00
vulkano-shaders Doc fixes (#1007) 2018-08-10 14:51:26 +02:00
vulkano-win Upgrade dependencies (#1012) 2018-08-10 14:50:38 +02:00
.gitignore Some work on the website 2017-06-27 18:18:42 +02:00
.gitlab-ci.yml Fix examples so that cargo test works 2016-04-15 18:05:58 +02:00
.gitmodules Make glslang work on Linux 2016-02-19 16:44:35 +01:00
.rustfmt.toml Run rustfmt on the code 2017-06-27 08:47:16 +02:00
.travis.yml Pass -j 1 flag to cargo test 2017-07-08 09:29:28 +02:00
Cargo.toml Some work on the website 2017-06-27 18:18:42 +02:00
CHANGELOG.md Upgrade dependencies (#1012) 2018-08-10 14:50:38 +02:00
DESIGN.md Update DESIGN.md 2017-04-18 12:49:01 +02:00
LICENSE-APACHE Add license everywhere 2016-03-26 10:17:37 +01:00
LICENSE-MIT Add license everywhere 2016-03-26 10:17:37 +01:00
logo.png Add the logo to the README (#779) 2017-08-27 10:04:37 +02:00
README.md Use libvulkan.dylib instead of MoltenVK by default on macOS (#948) 2018-04-19 09:48:33 +02:00
TROUBLES.md Add buffer_slice_field! macro 2016-05-02 11:18:26 +02:00

Vulkano

Crates.io Docs Build Status Gitter chat

See also vulkano.rs.

Vulkano is a Rust wrapper around the Vulkan graphics API. It follows the Rust philosophy, which is that as long as you don't use unsafe code you shouldn't be able to trigger any undefined behavior. In the case of Vulkan, this means that non-unsafe code should always conform to valid API usage.

What does vulkano do?

  • Provides a low-levelish API around Vulkan. It doesn't hide what it does, but provides some comfort types.
  • Plans to prevent all invalid API usages, even the most obscure ones. The purpose of vulkano is not to simply let you draw a teapot, but to cover all possible usages of Vulkan and detect all the possible problems in order to write robust programs. Invalid API usage is prevented thanks to both compile-time checks and runtime checks.
  • Can handle synchronization on the GPU side for you (unless you choose do that yourself), as this aspect of Vulkan is both annoying to handle and error-prone. Dependencies between submissions are automatically detected, and semaphores are managed automatically. The behavior of the library can be customized thanks to unsafe trait implementations.
  • Tries to be convenient to use. Nobody is going to use a library that requires you to browse the documentation for hours for every single operation.

Note that in general vulkano does not require you to install the official Vulkan SDK. This is not something specific to vulkano (you don't need the SDK to write programs that use Vulkan, even without vulkano), but many people are unaware of that and install the SDK thinking that it is required. However, macOS and iOS platforms do require a little more Vulkan setup since it is not natively supported. See below for more details.

Development status

Vulkano is still in heavy development and doesn't yet meet its goals of being very robust. However the general structure of the library is most likely definitive, and all future breaking changes will likely be straight-forward to fix in user code.

Documentation

To get started you are encouraged to read the examples in the vulkano-examples repository, starting with the triangle example.

macOS and iOS Setup

Vulkan is not natively supported by macOS and iOS. However, there exists MoltenVK a Vulkan implementation on top of Apple's Metal API. This allows vulkano to build and run on macOS and iOS platforms.

The easiest way to get vulkano up and running on macOS is to install the Vulkan SDK for macOS. Vulkano will by default, as it does on other platforms, look for libvulkan.1.dylib (included as part of the SDK). Note that it is still possible to link with the MoltenVK framework (as vulkano did in previous versions) by adding the appropriate cargo output lines to your build script and implementing your own vulkano::instance::loader::Loader that calls the MoltenVK vkGetInstanceProcAddr implementation.

On iOS vulkano links directly to the MoltenVK framework. There is nothing else to do besides installing it. Note that the Vulkan SDK for macOS also comes with the iOS framework.

Donate

Become a patron

Contributing

Contributions are welcome! Feel free to submit pull requests.

Pull requests that fix bugs or improve documentation are likely to be quickly reviewed, while pull requests that add features or change the API may be more controversial and take more time.

If your change adds, removes or modifies a trait or a function, please add an entry to the CHANGELOG.md file as part of your pull request.

Structure

This repository contains six libraries:

  • vulkano is the main one.
  • vulkano-shaders can analyse SPIR-V shaders at compile-time.
  • vulkano-shader-derive provides a custom derive that invokes vulkano-shaders. It lets you easily integrate your GLSL shaders within the rest of your source code.
  • vulkano-win provides a safe link between vulkano and the winit library which can create a window to render to.
  • glsl-to-spirv can compile GLSL to SPIR-V by wrapping around glslang. glsl-to-spirv is an implementation detail that you don't need to use manually if you use vulkano.
  • vk-sys contains raw bindings for Vulkan. You can use it even if you don't care about vulkano.

Once procedural macros are stabilized in Rust, the vulkano-shaders and vulkano-shader-derive crates will be merged with the vulkano crate. The glsl-to-spirv crate is an implementation detail of vulkano and is not supposed to be used directly if you use vulkano. You are, however, free to use it if you want to write an alternative to vulkano.

In order to run tests, run cargo test --all at the root of the repository. Make sure your Vulkan driver is up to date before doing so.

License

Licensed under either of

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you shall be dual licensed as above, without any additional terms or conditions.