Add "vtbl" option for low-level interface vtable generation #2845
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
windows-bindgen
crate's "sys" config option avoids generating bindings for COM interfaces since those necessarily require function bodies to implement virtual function calls, not directly supported by Rust. The "sys"-style bindings avoid generating function bodies to reduce build time.However in some rare cases, it can be useful to have the ability to call COM interfaces without having to manually define them all from scratch or generating full-blown COM interface support. This update introduces the "vtbl" option as a middle ground that may be used along with the "sys" option and will instruct the
windows-bindgen
crate to generate the IID and vtable layouts as follows:No functions are added, and you still have to go to the trouble of dereferncing a COM interface pointer, but at least the virtual function signatures are available for you to do so.
This is only available through the "vtbl" config option and does not affect the
windows
orwindows-sys
crates.