Update README.md
loaded/linked feature: correctly identify default, adjust order
This commit is contained in:
parent
84bf62b219
commit
fdaafe760a
|
@ -221,8 +221,9 @@ let pool = device.create_command_pool(&pool_create_info).unwrap();
|
||||||
|
|
||||||
### Optional linking
|
### Optional linking
|
||||||
|
|
||||||
The default `linked` cargo feature will link your binary with the Vulkan loader directly and expose the infallible `Entry::linked`.
|
The default `loaded` cargo feature will dynamically load the default Vulkan library for the current platform with `Entry::load`, meaning that the build environment does not have to have Vulkan development packages installed.
|
||||||
If your application can handle Vulkan being missing at runtime, you can instead enable the `loaded` feature to dynamically load Vulkan with `Entry::load`.
|
|
||||||
|
If, on the other hand, your application cannot handle Vulkan being missing at runtime, you can instead enable the `linked` feature, which will link your binary with the Vulkan loader directly and expose the infallible `Entry::linked`.
|
||||||
|
|
||||||
## Example
|
## Example
|
||||||
You can find the examples [here](https://github.com/MaikKlein/ash/tree/master/examples).
|
You can find the examples [here](https://github.com/MaikKlein/ash/tree/master/examples).
|
||||||
|
|
Loading…
Reference in a new issue