development/cargo
development/cargo
1
0
Fork 0
mirror of https://github.com/rust-lang/cargo synced 2024-10-14 19:52:45 +00:00
Code Issues Packages Projects Releases Wiki Activity
4852 commits 79 branches 101 tags 94 MiB
Rust 95.2%
Roff 4.4%
JavaScript 0.2%
Shell 0.1%
Find a file
bors 463e850146 Auto merge of #4570 - tatsuya6502:target-specific-artifacts, r=alexcrichton 
Handle target specific outputs such as .wasm or .dll.lib

Fixes #4500, #4535

Until now, Cargo does not have any knowledge about target-specific output files. It relies solely on rustc for this sort of information (`rustc --print=file-names ...`).

As a result, Cargo does not place some build artifacts (files) to target/{debug,release} directory. These files include *.wasm for wasm32-unknown-emscripten target and *.dll.lib for *-pc-windows-msvc cdylib target.

This commit will add such knowledge to Cargo so that *.wasm and *.dll.lib will be placed in target/{debug,release} directory.

**EDIT**: I added [a summary of changes](https://github.com/rust-lang/cargo/pull/4570#issuecomment-334433635). Please read it for more details of changes.

**IMPORTANT**
Although I added test cases for both wasm32-unknown-emscripten and *-pc-windows-msvc cdylib targets, ~I did not do manual testing on wasm32-unknown-emscripten target as I do not have an environment with emscripten installed. It will be appreciated if anybody tests this change for wasm32-unknown-emscripten target.~  **EDIT**: Tested for both wasm32-unknown-emscripten and x86_64-pc-windows-msvc. Thanks @Herschel for the help.
2017-10-09 20:48:17 +00:00
src Auto merge of #4570 - tatsuya6502:target-specific-artifacts, r=alexcrichton 2017-10-09 20:48:17 +00:00
tests Auto merge of #4570 - tatsuya6502:target-specific-artifacts, r=alexcrichton 2017-10-09 20:48:17 +00:00
.gitignore Proper building virtual manifest with -p flag 2017-07-27 22:51:05 +02:00
.travis.yml [travis] Enable cache for $HOME/.cargo/bin/ 2017-09-22 01:02:18 -07:00
appveyor.yml Work around AppVeyor for now 2017-07-20 08:56:49 -07:00
ARCHITECTURE.md Fix typos and reword slightly 2017-06-13 21:40:58 +03:00
Cargo.lock Update dependencies (unbreak macOS 10.13 with libgit2-sys-0.6.16) 2017-10-04 21:37:55 +02:00
Cargo.toml Use crypto-hash to calculate SHA256 2017-09-27 22:27:55 +09:00
CONTRIBUTING.md Describe E-mentor label in contributing.md 2017-10-02 22:11:09 +03:00
LICENSE-APACHE Add the standard Rust Apache/MIT license 2014-06-24 12:26:13 -07:00
LICENSE-MIT Remove inaccurate (misattributed) copyright notices 2017-07-26 17:19:24 -07:00
LICENSE-THIRD-PARTY Clean whitespace 2015-10-06 13:15:40 -04:00
README.md Update README.md 2017-09-30 11:18:22 +02:00

README.md

Cargo downloads your Rust project’s dependencies and compiles your project.

Learn more at http://doc.crates.io/

Code Status

Build Status Build 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.

Compiling from Source

Cargo requires the following tools and packages to build:

  • python
  • curl (on Unix)
  • cmake
  • OpenSSL headers (only for Unix, this is the libssl-dev package on ubuntu)
  • cargo and rustc

First, you'll want to check out this repository

git clone --recursive https://github.com/rust-lang/cargo
cd cargo

With cargo already installed, you can simply run:

cargo build --release

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.

Releases

High level release notes are available as part of Rust's release notes. Cargo releases coincide with Rust releases.

Reporting issues

Found a bug? We'd love to know about it!

Please report all issues on the github issue tracker.

Contributing

See CONTRIBUTING.md

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.