rust-cargo

I'm trying to build something which is using both hyper and git2 at the same time. Now I've got a problem with openssl being linked twice. A tip by shepmaster lead me to Cargos features and I tried that but I'm still stuck. The precise error I'm getting upon cargo build is the following: error: native library `openssl` is being linked to by more than one version of the same package, but it can only be linked once; try updating or pinning your dependencies to ensure that this package only shows up once openssl-sys v0.7.17 openssl-sys v0.9.1 As far as I can tell openssl is required both by git2

I know that the compiler can run directly on arm-linux-androideabi , but the Android emulator (I mean emulation of ARM on x86/amd64) is slow, so I don't want to use cargo and rustc on the emulator, I only want to run tests on it. I want to cross-compile tests on my PC ( cargo test --target=arm-linux-androideabi --no-run ?), and then upload and run them on emulator, hoping to catch bugs like this . How can I run cargo test without running cargo test ? Is it as simple as running all binaries that were built with cargo test --no-run ? kennytm There are two kinds of tests supported by cargo test ,

I wrote a little game using Rust, and I used cargo build --release to compile a release version on Mac. I tried to share this with my friend who is using Ubuntu, but when he tried to run the binary, he got the following error: cannot execute binary file: Exec format error I searched for this but found no answers. Doesn't Rust claim to have "no runtime"? Shouldn't it be able to run anywhere in binary form? Chris Emerson Rust not having a runtime means that it doesn't have a lot of code running as part of the language (for example a garbage collector or bytecode interpreter). It does still need

Suppose I execute cargo new one --bin and cargo new two --bin then add the same dependency to each project's Cargo.toml and build them. Now there are two absolutely identical sets of libraries: /one/target/debug/deps/ *.rlib /two/target/debug/deps/ *.rlib They are same files and waste storage space, but really the problem is that I have to compile these libraries again for every project. It takes a very much time. There is the same problem with cargo install . Can I specify a place to store compiled libraries to avoid recompilation? Several Cargo projects might share the libraries by using the

In trying to write an optimized DSP algorithm, I was wondering about relative speed between stack allocation and heap allocation, and size limits of stack-allocated arrays. I realize there is a stack frame size limit, but I don't understand why the following runs, generating seemingly realistic benchmark results with cargo bench , but fails with a stack overflow when run with cargo test --release . #![feature(test)] extern crate test; #[cfg(test)] mod tests { use test::Bencher; #[bench] fn it_works(b: &mut Bencher) { b.iter(|| { let stack = [[[0.0; 2]; 512]; 512]; }); } } kennytm To get things

I have a small project which built with no issues when it was all in one big .rs file. I wanted to make it easier to work with, so I broke it up into modules, and the project is now structured like this: ├── GameState │ ├── ballstate.rs │ ├── collidable.rs │ ├── gamestate.rs │ ├── mod.rs │ └── playerstate.rs ├── lib.rs └── main.rs In ballstate.rs , I need to use the rand crate. Here's an abbreviated version of the file: extern crate rand; pub struct BallState { dir: Point, frame: BoundingBox } impl BallState { fn update_dir(&mut self) { use rand::*; let mut rng = rand::thread_rng(); self.dir.x