Use Cargo's "Build Script Support" and include PortAudio with the repo as a static lib.

[mitchmindtree]

I'm unsure how tricky this would be, but it would be awesome if we could have Cargo automatically handle the downloading and installation of the PortAudio lib - would make it much easier for other Rusty users to pick our libs :)

The info on Cargo's build script support is here.

[jeremyletang]

Hey i've think about this but i'm not sur it's a good idea to download a library for the user and install it for jim. But maybe we can built a static libraty wich will be preferable maybe ?

[mitchmindtree]

Yeah fair call 👍 a static library could be sweet :) That way we can always be sure we have the right version on hand too

[mitchmindtree]

Just as a bump of motivation for us, I posted sound_stream to HN last night, and the dependency upon having PortAudio installed was the main critique. Here's a link to the post.

[jeremyletang]

hey i've just see this, see #37

[bvssvni]

The way we do it in the FreeType library is that we got one repo freetype-sys which wraps the low level API and one repo freetype-rs for the higher level bindings https://github.com/pistondevelopers/freetype-rs

You can reexport the ffi module without breaking backward compability. One important thing is to add "links" to the Cargo.toml in the -sys project.

I believe the way both projects build is similar, so perhaps we could copy the way freetype-rs does it?