rust-windows-dll
winapi-rs
Our great sponsors
rust-windows-dll | winapi-rs | |
---|---|---|
1 | 14 | |
21 | 1,779 | |
- | - | |
0.0 | 0.0 | |
8 months ago | 9 months ago | |
Rust | Rust | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rust-windows-dll
-
Rust for Windows Bindings: Generating the Entire Windows API Surface from Metadata
https://github.com/thisKai/rust-windows-dll is quite convenient.
winapi-rs
-
Improving Interoperability Between Rust and C++
Vtables are pretty solved as well. I do a lot of Windows COM interop. Using the `windows` crate, vtables for COM interfaces are relegated to an implementation detail - instead you simply implement a (typically safe!) trait:
https://microsoft.github.io/windows-docs-rs/doc/windows/Win3...
Which can then be converted to a refcounted smart pointer:
https://microsoft.github.io/windows-docs-rs/doc/windows/Win3...
All driven by win32 sdk parsing and metadata.
But suppose we want to roll our own, because we tend to prefer `winapi` but it lacks definition. That's not too terrible either:
• https://github.com/MaulingMonkey/thindx-xaudio2/blob/master/...
• https://github.com/MaulingMonkey/thindx-xaudio2/blob/master/...
• https://github.com/MaulingMonkey/thindx-xaudio2/blob/master/...
I could more heavily lean on my macros ala `windows`, but I went the route of manual control for better doc comments, more explicit control of thread safety traits to match the existing C++ codebase, etc.
Is there some pointer casting? Yes. Is it annoying or likely to be what breaks? No. What is annoying?
• Stacked borrows and narrowing spatial provenance ( https://github.com/retep998/winapi-rs/issues/1025 - this can be "solved" by sticking to pointers ala `windows`, or by choosing a different provenance model like rustc might be doing?)
• Guarding against panics unwinding over an FFI boundary. This is at least being worked on, but remains unfinished ( https://rust-lang.github.io/rfcs/2945-c-unwind-abi.html )
• Edge case ABI weirdness specific to C++ methods ( https://devblogs.microsoft.com/oldnewthing/20220113-00/?p=10... , https://github.com/retep998/winapi-rs/issues/523 )
-
Trying to compile rust library on Windows
Is winapi = { version = "0.3.9", features = ["winuser"] } in [target.'cfg(windows)'.dependencies]? All the missing symbols are functions in module winapi::um::wincrypt (see https://docs.rs/winapi/0.3.9/winapi/um/wincrypt/index.html#functions ) and the crate's Git repo at https://github.com/retep998/winapi-rs contains all the import libs and export defs for the corresponding DLLs in directory x86_64. As crypt32.dll ships with windows by default, I think this is all that would be needed for building on a windows PC.
-
Kernel Headers for Windows could soon make it into windows-rs
This would be a community driven project for now but I have high hopes considering we already had projects like winapi and Trantect/winapi-rs.
-
More malware is shifting to Rust
Can't you choose to control what OS APIs you use if you use crates such as libc and winapi, or just directly using extern "C" { ... }/extern "system" { ... }, or even inline assembly for syscalls with llvm_asm! or asm!?
-
Hey Rustaceans! Got an easy question? Ask here (23/2021)!
What is the difference between the winapi crate and the windows crate? Are they the same thing, and is one better than the other?
-
The playable demo of Outer Wonders, our cute, colorful and Rust-powered puzzle game, is live on itch.io for Windows and Linux! Thank you Rust community for creating such awesome tools!
Turns out OpenGL and Vulkan sometimes behave weirdly on Windows machines (some OpenGL drivers use a huge amount of CPU power and create unexpected sync points; I also ran into this very weird driver crash while testing our Vulkan-powered version of Outer Wonders which is scary), so we implemented Direct3D 11 support using the winapi crate, which was much of a relief (D3D11 is an ideal rendering API when it comes to supporting Windows because it allows you target hardware with Windows versions going as far back as Vista, and from my experience, Direct3D drivers have a more consistent and reliable behavior). We didn't have to bring significant changes to our abstraction layer to add Direct3D 11 support.
-
"Pure Rust" tag (Discussion)
The only exceptions would be those (ideally) manually reviewed "bedrock" crates like winapi
-
Rust for Windows
The windows crate is Microsoft's own first-party option for writing Rust code against Windows' native APIs. The winapi crate was previously a popular community-built option. It works slightly differently than the official one. My understanding is that the official one requires that you have a Windows SDK installed in addition to the Rust toolchain, and that the Rust compiler builds the bindings to that SDK on-demand. (That's what the nested bindings library is for in this video.) The winapi crate, on the other hand, is the bindings, prebuilt and ready to use. On one hand, this is probably easier for you, the application developer, to use; on the other hand, it probably also requires more human effort by the library maintainers to add support for new APIs.
The winapi does a lot of work to support that use-case. Importantly, it ships (mingw) import libraries to allow linking against windows libs from linux trivially[0].
[0]: https://github.com/retep998/winapi-rs/tree/0.3/x86_64/def
-
Rust for Windows Bindings: Generating the Entire Windows API Surface from Metadata
As far as I could understand, this crate provides unsafe bindings for the Win32 API in Rust, which is the same thing that winapi does, except that everything is automatically generated from existent Win32 metadata, while winapi does everything by hand.
What are some alternatives?
windows-rs - Rust for Windows
Cargo - The Rust package manager
rust-dyn-call - Do not use. Do not use. Do not use. (Calls a function dynamically)
rand - A Rust library for random number generation.
core-foundation-rs - Rust bindings to Core Foundation and other low level libraries on Mac OS X and iOS
rust-sdl2 - SDL2 bindings for Rust
sys-mount - High level FFI binding around the sys mount & umount2 calls, for Rust
full_search - Flutter full-text search plugin build on Tantivy supports async。 基于 Tantivy 实现的 Flutter 本地全文搜索插件(支持 async)
flac-lame-frontend - A native Win32 GUI to work with FLAC and LAME command line tools.
winsafe - Windows API and GUI in safe, idiomatic Rust.
MSRC-Security-Research - Security Research from the Microsoft Security Response Center (MSRC)
send-to-start - A tool to add programs to Windows Start menu search without pinning them