Geobert Quach

I managed to test the PR and it works after doing: - Get `libusb` from http://libusb.info/ - create a `libusb` folder somewhere - inside, create a `lib` and an `include`...

I talk too fast, `cargo check` passes, but not `cargo build` after putting the example code. Linking is failing with: ``` error: linking with `link.exe` failed: exit code: 1120 |...

From what I can gather, we may need `legacy_stdio_definitions.lib` How de we pass this kind of information in Rust?

As a test, I've put `legacy_stdio_definitions.lib` in the libusb/lib folder and added `println!("cargo:rustc-link-lib=static=legacy_stdio_definitions");` to the build.rs and I got rid of some unresolved symbols and have only one left:  ```...

Ok, I've done more tries and here are my results. Using the binary provided by `libusb.info`, I got the link errors above. These errors seems to happen because of different...

I'm dumb: while rebuilding libusb, I forgot to set it to x64… So we have to rebuild libusb ourself in order to use it with VS2015 toolchain In conclusion, the...

If I recall properly, I hacked into the .cargo folder to see if something can come out and I don't use libusb anymore so I didn't reach the phase to...

I'm using hidapi

As I said, I've done an ugly hack by tampering the files in .cargo but I can't remember what as I didn't use libusb in the end. Sorry :-/

I'd like to test it but I'm not very familiar with manipulation on github: what do I need to do? First, fork libusb-sys of course and then how do I...