SoundStream – A simple-as-possible, fast audio I/O stream for Rust
1–10 of 12 posts
Re: SoundStream – A simple-as-possible, fast audio I/O stream for Rust
#2I've seen many discussions here about rechanging the api of the libraries since they were expecting features from the language.
Re: SoundStream – A simple-as-possible, fast audio I/O stream for Rust
#3When is this language expected to go 1.0 ? I've seen many discussions here about rechanging the api of the libraries since they were expecting features from the language.
Re: SoundStream – A simple-as-possible, fast audio I/O stream for Rust
#4> SoundStream requires that you have the PortAudio lib installed on your system
Meh.
Theres really no excuse, given cargo now has proper support for building cross platform dependencies.
My least favourite thing about rust is trying to use a crate only to find 'author assumed you already had dependencies installed. sorry'
Re: SoundStream – A simple-as-possible, fast audio I/O stream for Rust
#5This is neat, but... > SoundStream requires that you have the PortAudio lib installed on your system Meh. Theres really no excuse, given cargo now has proper support for building cross platform dependencies. My least favourite thing about rust is trying to use a crate only to find 'author assumed you already had dependencies installed. sorry'
Re: SoundStream – A simple-as-possible, fast audio I/O stream for Rust
#6This is neat, but... > SoundStream requires that you have the PortAudio lib installed on your system Meh. Theres really no excuse, given cargo now has proper support for building cross platform dependencies. My least favourite thing about rust is trying to use a crate only to find 'author assumed you already had dependencies installed. sorry'
Re: SoundStream – A simple-as-possible, fast audio I/O stream for Rust
#7This is neat, but... > SoundStream requires that you have the PortAudio lib installed on your system Meh. Theres really no excuse, given cargo now has proper support for building cross platform dependencies. My least favourite thing about rust is trying to use a crate only to find 'author assumed you already had dependencies installed. sorry'
I've talked with the author of the PortAudio bindings and we're planning on including a static lib with the repo instead (along with a cargo build script), so that should hopefully make it as easy to use as any other crate.
Re: SoundStream – A simple-as-possible, fast audio I/O stream for Rust
#8This is neat, but... > SoundStream requires that you have the PortAudio lib installed on your system Meh. Theres really no excuse, given cargo now has proper support for building cross platform dependencies. My least favourite thing about rust is trying to use a crate only to find 'author assumed you already had dependencies installed. sorry'
Re: SoundStream – A simple-as-possible, fast audio I/O stream for Rust
#9This is neat, but... > SoundStream requires that you have the PortAudio lib installed on your system Meh. Theres really no excuse, given cargo now has proper support for building cross platform dependencies. My least favourite thing about rust is trying to use a crate only to find 'author assumed you already had dependencies installed. sorry'
Your least favourite thing is having to {apt-get|yum|pkg|whatever} install somelib[-dev] ?
Re: SoundStream – A simple-as-possible, fast audio I/O stream for Rust
#10This is neat, but... > SoundStream requires that you have the PortAudio lib installed on your system Meh. Theres really no excuse, given cargo now has proper support for building cross platform dependencies. My least favourite thing about rust is trying to use a crate only to find 'author assumed you already had dependencies installed. sorry'
Compiling external dependencies is non-trivial, even though cargo gives the bare minimum of tools to make it possible. I think it's unreasonable to expect rust to construct it's own replica of distribution's packages for C/C++ code. To my knowledge no other language has a package manager or repository which does this, or even attempts to.
That can be via package manager, pkg-config, static library download, building them, or via prompting the user to install them manually.
Since rust supports the #[cfg(target="foo")] in build scripts, you can even implement your solution for just one platform, and then slowly add additional platform support as people demand it.
A message like: "Hey, your platform isn't supported by our build script; submit a bug at ... if you'd like to get support added. We welcome push requests". For example, android support is probably not a target for most crates, but it may be an important target in the future for many libraries. ...and building a cross-compiled android binary is a LOT more involved than just an 'apt-get install foo'.
Just failing? Nope.