mirror/vk-bootstrap
1
0
Fork 0
mirror of https://github.com/charles-lunarg/vk-bootstrap.git synced 2024-11-22 07:24:34 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix getting started docs using pointer instead of reference

Browse Source 
add_required_extension_features takes a reference now, but the docs
indicated it took a pointer.
This commit is contained in:
Charles Giessen 2024-04-26 15:01:09 -05:00 committed by Charles Giessen
parent 50b75222b2
commit e186301249
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/getting_started.md
View File

@ -182,7 +182,7 @@ Features only available through extensions need to use `add_required_extension_f
VkPhysicalDeviceDescriptorIndexingFeatures descriptor_indexing_features{}; VkPhysicalDeviceDescriptorIndexingFeatures descriptor_indexing_features{};
descriptor_indexing_features.<features_used> = true; descriptor_indexing_features.<features_used> = true;
phys_device_selector.add_required_extension_features(&descriptor_indexing_features); phys_device_selector.add_required_extension_features(descriptor_indexing_features);
``` ```
The features and extensions used as selection criteria in `vkb::PhysicalDeviceSelector` automatically propagate into `vkb::DeviceBuilder`. That means the application only needs to state the feature requirement once, and `vk-bootstrap` will handle enabling it on the resulting device. The features and extensions used as selection criteria in `vkb::PhysicalDeviceSelector` automatically propagate into `vkb::DeviceBuilder`. That means the application only needs to state the feature requirement once, and `vk-bootstrap` will handle enabling it on the resulting device.