Name | Date | Size | #Lines | LOC | ||
---|---|---|---|---|---|---|
.. | 03-May-2022 | - | ||||
ci/ | H | 03-May-2022 | - | 8 | 4 | |
src/ | H | 03-May-2022 | - | 578 | 308 | |
.cargo-checksum.json | H A D | 03-May-2022 | 89 | 1 | 1 | |
.cargo_vcs_info.json | H A D | 01-Jan-1970 | 74 | 6 | 5 | |
.gitignore | H A D | 24-Aug-2018 | 35 | 5 | 4 | |
.travis.yml | H A D | 24-Aug-2018 | 97 | 9 | 8 | |
COPYING | H A D | 17-Aug-2018 | 126 | 4 | 2 | |
Cargo.toml | H A D | 01-Jan-1970 | 1.2 KiB | 28 | 26 | |
Cargo.toml.orig-cargo | H A D | 27-Jan-2019 | 711 | 28 | 26 | |
LICENSE-MIT | H A D | 17-Aug-2018 | 1.1 KiB | 22 | 17 | |
README.md | H A D | 27-Jan-2019 | 1.7 KiB | 52 | 34 | |
UNLICENSE | H A D | 17-Aug-2018 | 1.2 KiB | 25 | 20 | |
appveyor.yml | H A D | 19-Aug-2018 | 605 | 27 | 26 |
README.md
1winapi-util 2=========== 3This crate provides a smattering of safe wrappers around various parts of the 4[winapi](https://crates.io/crates/winapi) crate. 5 6[![Linux build status](https://api.travis-ci.org/BurntSushi/winapi-util.png)](https://travis-ci.org/BurntSushi/winapi-util) 7[![Windows build status](https://ci.appveyor.com/api/projects/status/github/BurntSushi/winapi-util?svg=true)](https://ci.appveyor.com/project/BurntSushi/winapi-util) 8[![](http://meritbadge.herokuapp.com/winapi-util)](https://crates.io/crates/winapi-util) 9 10Dual-licensed under MIT or the [UNLICENSE](http://unlicense.org). 11 12 13### Documentation 14 15https://docs.rs/winapi-util 16 17 18### Usage 19 20Add this to your `Cargo.toml`: 21 22```toml 23[dependencies] 24winapi-util = "0.1" 25``` 26 27and this to your crate root: 28 29```rust 30extern crate winapi_util; 31``` 32 33 34### Notes 35 36This crate was born out of frustration with having to write lots of little 37ffi utility bindings in a variety of crates in order to get Windows support. 38Eventually, I started needing to copy & paste a lot of those utility routines. 39Since they are utility routines, they often don't make sense to expose directly 40in the crate in which they are defined. Instead of continuing this process, 41I decided to make a crate instead. 42 43Normally, I'm not a huge fan of "utility" crates like this that don't have a 44well defined scope, but this is primarily a practical endeavor to make it 45easier to isolate Windows specific ffi code. 46 47While I don't have a long term vision for this crate, I will welcome additional 48PRs that add more high level routines/types on an as-needed basis. 49 50**WARNING:** I am not a Windows developer, so extra review to make sure I've 51got things right is most appreciated. 52