0863469c8b
Previously Cargo would compile a library into a different location depending on whether it was the "root crate" or not. In the ongoing saga of reducing Cargo's reliance on the idea of a "root crate" this PR is the next step. With workspaces the root crate of a compliation changes all the time, so the output needs to be the same whether a crate is at the root or not. Fixing this inconsistence in turn fixes bugs like #2855 and #2897 which arise due to this discrepancy. Additionally, Cargo will no longer recompile a library when it's used as a "root crate" or not. This is fixed by taking a few steps: * Everything is now compiled into the `deps` directory, regardless of whether it's a root output or not. * If a "root crate" is being compiled, then the relevant outputs are hard-linked up one level to where they are today. This means that your binaries, dylibs, staticlibs, etc, will all show up where they used to. * The `-C metadata` flag is always omitted for path dependencies now. These dependencies are always path dependencies and already all have unique crate names. Additionally, they're the only crates in the DAG without metadata, so there's no need to provide additional metadata. This in turn means that none of the file names of the generated crates are mangled. Closes #2855 |
||
|---|---|---|
| src | ||
| tests | ||
| .gitignore | ||
| .gitmodules | ||
| .travis.install.deps.sh | ||
| .travis.yml | ||
| appveyor.yml | ||
| Cargo.lock | ||
| Cargo.toml | ||
| configure | ||
| LICENSE-APACHE | ||
| LICENSE-MIT | ||
| LICENSE-THIRD-PARTY | ||
| Makefile.in | ||
| README.md | ||
Cargo downloads your Rust project’s dependencies and compiles your project.
Learn more at http://doc.crates.io/
Code Status
Installing Cargo
Cargo is distributed by default with Rust, so if you've got rustc installed
locally you probably also have cargo installed locally.
If, however, you would like to install Cargo from the nightly binaries that are
generated, you may also do so! Note that these nightlies are not official
binaries, so they are only provided in one format with one installation method.
Each tarball below contains a top-level install.sh script to install Cargo.
x86_64-unknown-linux-gnui686-unknown-linux-gnux86_64-apple-darwini686-apple-darwinx86_64-pc-windows-gnui686-pc-windows-gnux86_64-pc-windows-msvc
Note that if you're on Windows you will have to run the install.sh script from
inside an MSYS shell, likely from a MinGW-64 installation.
Compiling from Source
Cargo requires the following tools and packages to build:
pythoncurl(on Unix)cmake- OpenSSL headers (only for Unix, this is the
libssl-devpackage on ubuntu)
First, you'll want to check out this repository
git clone --recursive https://github.com/rust-lang/cargo
cd cargo
If you already have rustc and cargo installed elsewhere, you can simply run
cargo build --release
Otherwise, if you have rustc installed and not Cargo, you can simply run:
./configure
make
make install
If, however, you have neither rustc nor cargo previously installed you can
run:
python -B src/etc/install-deps.py
./configure --local-rust-root="$PWD"/rustc
make
make install
Note: if building for 32 bit systems run BITS=32 python -B ..
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
Adding new subcommands to Cargo
Cargo is designed to be extensible with new subcommands without having to modify Cargo itself. See the Wiki page for more details and a list of known community-developed subcommands.
Contributing to the Docs
To contribute to the docs, all you need to do is change the markdown files in
the src/doc directory. To view the rendered version of changes you have
made locally, run:
./configure
make doc
open target/doc/index.html
Release notes
High level release notes are available as part of Rust's release notes.
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.
Third party software
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).
In binary form, this product includes software that is licensed under the terms of the GNU General Public License, version 2, with a linking exception, which can be obtained from the upstream repository.