rust-cargo

I want to run the following commands side by side cargo watch "check" cargo watch "build" I want to run cargo watch build in the background and use cargo watch check to look at the error messages. The problem is that cargo watch check always runs after cargo watch build and then also needs to wait on the file lock cargo check Blocking waiting for file lock on build directory I don't think that a file lock would be required for cargo check. Is it possible to disable file locking in cargo? malbarbo I don't think that a file lock would be required for cargo check. I can think of in one reason:

I have src/bin/linux-only.rs which does some things which work on Linux only (e.g. libc bindings which only exist on Linux). I want to exclude that file from being built on OS X. I started putting #[cfg(target_os = "linux")] on every block in linux-only.rs but that is cluttering up the source code beyond any reason. Is there a nicer way to do this? Writing #![cfg(target_os = "linux")] (note the exclamation mark) at the top of the file will work for the whole file (as long as it contains a single module), not just for the next block (item). Source: Rust reference . Edit : if you can move that

According to its manual , Cargo packages can have multiple executable targets, but only one library target is allowed. A package can contain zero or one library crates and as many binary crates as you’d like. There must be at least one crate (either a library or a binary) in a package. Why is it limited to one? What are the reasons and benefits? Cargo is primarily a package manager. Thus, the primary role of a package is to define a library. When we use a crate as a dependency, we only specify the package name in our Cargo.toml . Since there can be at most one library, Cargo doesn't need you

I think this is a very common issue among those who want to use Cargo with Windows at work; I have seen multiple GitHub issues and forum posts related to it, but none of the answers solved my problems. Whenever I try to build some code pointing to a crates.io crate, I get the following error: Downloading <package> error: unable to get packages from source Caused by: failed to download package <package> from <package address> Caused by: SSL connect error What can I do to fix this? I know that Cargo can use the settings at .cargo/config and that the proxy details can be included there, but it

I just installed Rust on my Mac and rustc --version --verbose displays rustc 1.0.0-nightly (91bdf23f5 2015-03-09) (built 2015-03-08) binary: rustc commit-hash: 91bdf23f504f79ed59617cde3dfebd3d5e39a476 commit-date: 2015-03-09 build-date: 2015-03-08 host: x86_64-apple-darwin release: 1.0.0-nightly I cloned a couple of repositories ( postgres-extension and erlang-rust-nif ) and ran cargo build upon both of them. Both reported the error error: could not exec the linker `cc`: No such file or directory (os error 2) error: aborting due to previous error Additionally, I wasn't able to compile a simple

The default file-tree created by Cargo allows parallel compilation of release and debug builds as they are located in their own directories; target/release and target/debug , respectively. How difficult is it to also allow parallel compilation of stable / nightly -compiler. For example using the directories target/debug/stable target/debug/nightly I am aware it can be done with jails/containers, but I was hoping for a somewhat more Cargo-ish solution. Modern Rust I believe that your main problem of rebuilding dependencies no longer exists: $ cargo +nightly build Updating crates.io index