Handle target specific outputs such as .wasm or .dll.lib
authorTatsuya Kawano <tatsuya@hibaridb.org>
Tue, 3 Oct 2017 11:44:35 +0000 (19:44 +0800)
committerTatsuya Kawano <tatsuya@hibaridb.org>
Tue, 3 Oct 2017 11:44:35 +0000 (19:44 +0800)
commitc4b56e2a34662bc93012af1d3bc2e7c1c6d46406
treeb1d12d426e584f4e4bd89fcbda11290290e61218
parentd7e3b7f24265016c9ce4455504b914dc92c92b07
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.
src/cargo/ops/cargo_rustc/context.rs [changed mode: 0755->0644]
tests/build.rs