c0127391bf
The previous logic for recompiling any dependency was almost entirely based on the mtimes of the relevant input files. This isn't quite what's desired for git and registry dependencies because the mtime could be fluctuating while the files aren't changing. For example: 1. Project A checks out git repo C at revision C1 2. Project A builds, records mtimes of C 3. Project B checks out git repo C at revision C2 4. Project B builds, records new mtimes of C 5. Project A is rebuilt, rebuilding C b/c mtimes are different In step 5 here C should not be rebuilt because the revision didn't actually change. This commit alters git/registry dependencies to completely bypass the --dep-info emitted and only rely on the git/registry source to inform what the fingerprint is. This is the revision/version, respectively, and should be all that's necessary to track changes to the repo and trigger a rebuild. |
||
|---|---|---|
| DESIGN | ||
| src | ||
| tests | ||
| .gitignore | ||
| .travis.install.deps.sh | ||
| .travis.yml | ||
| .vimrc | ||
| Cargo.lock | ||
| Cargo.toml | ||
| configure | ||
| LICENSE-APACHE | ||
| LICENSE-MIT | ||
| Makefile.in | ||
| MANIFEST.md | ||
| README.md | ||
Cargo downloads your Rust project’s dependencies and compiles your project.
Learn more at http://crates.io/.
Installing cargo from nightlies
Cargo has nightlies available for use. The cargo source is not always guaranteed to compile on rust master as it may lag behind by a day or two. Nightlies, however, will run regardless of this fact!
triple=x86_64-unknown-linux-gnu
curl -O http://static.rust-lang.org/cargo-dist/cargo-nightly-$triple.tar.gz
tar xf cargo-nightly-$triple.tar.gz
./cargo-nightly-$triple/install.sh
Nightlies are available for the following triples:
x86_64-unknown-linux-gnui686-unknown-linux-gnux86_64-apple-darwini686-apple-darwini686-pc-mingw32
Note that if you're using the windows snapshot you will need Mingw-w64 installed as well as MSYS. The installation script needs to be run inside the MSYS shell.
Compiling cargo
Cargo requires the following tools and packages to build:
rustcpythoncurlorwgetcmakepkg-config- OpenSSL headers (
libssl-devpackage on ubuntu)
Cargo can then be compiled like many other standard unix-like projects:
git clone https://github.com/rust-lang/cargo
cd cargo
./configure
make
make install
More options can be discovered through ./configure, such as compiling cargo
for more than one target. For example, if you'd like to compile both 32 and 64
bit versions of cargo on unix you would use:
$ ./configure --target=i686-unknown-linux-gnu,x86_64-unknown-linux-gnu
Contributing to the Docs
To contribute to the docs, please submit pull requests to wycats/cargo-website. All you need to do is change the markdown files in the source directory.
Reporting Issues
Found a bug? We'd love to know about it!
Please report all issues on the github issue tracker.
License
Cargo is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0).
See LICENSE-APACHE and LICENSE-MIT for details.