#windows #winapi #util #win

winapi-util

A dumping ground for high level safe wrappers over winapi

3 releases

0.1.2 Jan 27, 2019
0.1.1 Aug 25, 2018
0.1.0 Aug 25, 2018

#9 in Windows APIs

Download history 17491/week @ 2018-12-20 17177/week @ 2018-12-27 21347/week @ 2019-01-03 21372/week @ 2019-01-10 21621/week @ 2019-01-17 25039/week @ 2019-01-24 25831/week @ 2019-01-31 28883/week @ 2019-02-07 27542/week @ 2019-02-14 29477/week @ 2019-02-21 30206/week @ 2019-02-28 31012/week @ 2019-03-07 28978/week @ 2019-03-14 26264/week @ 2019-03-21 28228/week @ 2019-03-28

84,334 downloads per month
Used in 1,865 crates (6 directly)

Unlicense/MIT

21KB
312 lines

winapi-util

This crate provides a smattering of safe wrappers around various parts of the winapi crate.

Linux build status Windows build status

Dual-licensed under MIT or the UNLICENSE.

Documentation

https://docs.rs/winapi-util

Usage

Add this to your Cargo.toml:

[dependencies]
winapi-util = "0.1"

and this to your crate root:

extern crate winapi_util;

Notes

This crate was born out of frustration with having to write lots of little ffi utility bindings in a variety of crates in order to get Windows support. Eventually, I started needing to copy & paste a lot of those utility routines. Since they are utility routines, they often don't make sense to expose directly in the crate in which they are defined. Instead of continuing this process, I decided to make a crate instead.

Normally, I'm not a huge fan of "utility" crates like this that don't have a well defined scope, but this is primarily a practical endeavor to make it easier to isolate Windows specific ffi code.

While I don't have a long term vision for this crate, I will welcome additional PRs that add more high level routines/types on an as-needed basis.

WARNING: I am not a Windows developer, so extra review to make sure I've got things right is most appreciated.

Dependencies

~531KB

  • windows winapi 0.3+std+consoleapi+errhandlingapi+fileapi+minwindef+processenv+winbase+wincon+winerror+winnt