Struct openxr::Entry [−][src]
pub struct Entry { /* fields omitted */ }
Expand description
Entry point to the API. Start here.
An Entry
represents access to an OpenXR implementation. When the crate is built with the
linked
feature, this can be obtained at compile time with the linked
constructor. The
static
feature provides a built-in copy of the Khronos OpenXR loader for use in this
pattern. Alternatively, the loaded
feature exposes the load
and load_from
constructors to
manually load an OpenXR implementation at run-time.
Implementations
Access entry points linked directly into the binary at compile time
Available if the linked
feature is enabled. You must ensure that the entry points are
actually linked into the binary, e.g. by enabling the static
feature or manually linking
to an external loader or implementation.
Load entry points at run time from the dynamic library openxr_loader
according to the
target platform’s naming conventions
Available if the loaded
feature is enabled.
Load entry points at run time from the dynamic library identified by path
Available if the loaded
feature is enabled.
pub fn create_instance(
&self,
app_info: &ApplicationInfo<'_>,
required_extensions: &ExtensionSet,
layers: &[&str]
) -> Result<Instance>
pub fn create_instance(
&self,
app_info: &ApplicationInfo<'_>,
required_extensions: &ExtensionSet,
layers: &[&str]
) -> Result<Instance>
Create an OpenXR instance with certain extensions enabled. Android support can be enabled by
setting khr_android_create_instance
to true
.
Most applications will want to enable at least one graphics API extension
(e.g. khr_vulkan_enable2
) so that a Session
can be created for rendering.
Determine the set of extensions supported by this OpenXR implementation
Trait Implementations
Auto Trait Implementations
impl RefUnwindSafe for Entry
impl UnwindSafe for Entry
Blanket Implementations
Mutably borrows from an owned value. Read more