Make available in crates io ?

I'm actively working on the crate again, so "soon." My rough checklist for a 0.1 release of fmod-rs and versioned releases of the sys crates:

[ ] Email Firelight Technologies to clarify the legal ability to distribute language bindings (#15). I don't want to get into legal issues, obviously.
[ ] Make a users.rust-lang post asking for opinions on the structure for the sys crates. I think the current setup is reasonable enough, but I want another dev's input before committing, since for the versioning to work out usefully they're getting published with 2.X versions immediately and thus lack the space for later breaking changes to how the buildscript works.
[ ] Pull out my Mac and figure out if there exists a default install location that the sys crates can search when link-search is enabled.
[ ] Cover the remaining core API surface which is mostly a mechanical process to do (https://github.com/CAD97/fmod-rs/milestone/1, Geometry and Reverb3D).
[ ] Port the remaining FMOD Core examples (#13).

The first and the last ones are the firm requirements. Legal for obvious CYA reasons, and the examples to show that the bindings are complete enough to be properly useful. I'll estimate that the crate should be ready to be published before the end of July, just pending if I hear back from Firelight Technologies before then.

Until then, the bindings' code is publicly accessible in this repo and OSS licensed, so I can't stop anyone from using it. It's full intent to redistribute (i.e. on crates-io) that I want to get clearance for before doing.

CAD97 / fmod-rs

Make available in crates io ? #14