You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First off, thanks for this crate. It is a lifesaver dealing with winapi!
As much as windows is poised to be a worthy successor to the "autogenerated low-level bindings to Windows APIs" problem, I'm stuck with winapi for the moment (until I can figure out how to turn a .tlb into a .winmd inside build.rs using only pure-rust or standard MSVC tools; COM bindings for a 3rd party, closed source program with unclear licensing to redistribute type library). This is my first serious foray into FFI/unsafe in Rust, with a limited amount of previous COM-in-Python (yuck) experience, and your project has been a good guide. It's instructive to see the difference between my first-order attempts at safe wrappers and the stuff in here (after I discovered it).
The latest release on crates.io is over two years old. It only has com, error, and wide modules uncommented. I'd prefer not to use git sources in my Cargo.toml, but I'll survive in the meantime :) It makes pinning a version more of a pain, as well as discovering when there are new compatible/incompatible changes and fixes. Semver spoils us.
The text was updated successfully, but these errors were encountered:
First off, thanks for this crate. It is a lifesaver dealing with
winapi
!As much as
windows
is poised to be a worthy successor to the "autogenerated low-level bindings to Windows APIs" problem, I'm stuck withwinapi
for the moment (until I can figure out how to turn a .tlb into a .winmd insidebuild.rs
using only pure-rust or standard MSVC tools; COM bindings for a 3rd party, closed source program with unclear licensing to redistribute type library). This is my first serious foray into FFI/unsafe in Rust, with a limited amount of previous COM-in-Python (yuck) experience, and your project has been a good guide. It's instructive to see the difference between my first-order attempts at safe wrappers and the stuff in here (after I discovered it).The latest release on crates.io is over two years old. It only has
com
,error
, andwide
modules uncommented. I'd prefer not to use git sources in myCargo.toml
, but I'll survive in the meantime :) It makes pinning a version more of a pain, as well as discovering when there are new compatible/incompatible changes and fixes. Semver spoils us.The text was updated successfully, but these errors were encountered: