coreutils/src/mv/Cargo.toml

[package]
name = "mv"
version = "0.0.1"
authors = []

[lib]
name = "uu_mv"
path = "mv.rs"

[dependencies]
getopts = "0.2.14"
uucore = { path="../uucore" }

[[bin]]
name = "mv"
path = "main.rs"
Basic Cargo build Builds the uutils multicall binary containing all utils (except stdbuf) by default. To only build a subset `cargo --no-default-features --features <utils>` can be used. Whats missing is building the standalone binaries and a mechanism to automatically disable the build of unix only utils on windows. 2015-07-31 22:49:14 +00:00			`[package]`
			`name = "mv"`
			`version = "0.0.1"`
			`authors = []`

			`[lib]`
Refactor and simplify build for utilities. For coreutils, there are two build artifacts: 1. multicall executable (each utility is a separate static library) 2. individual utilities (still separate library with main wrapper) To avoid namespace collision, each utility crate is defined as "uu_{CMD}". The end user only sees the original utility name. This simplifies build.rs. Also, the thin wrapper for the main() function is no longer contained in the crate. It has been separated into a dedicated file. This was necessary to work around Cargo's need for the crate name attribute to match the name in the respective Cargo.toml. 2015-12-08 02:42:08 +00:00			`name = "uu_mv"`
Basic Cargo build Builds the uutils multicall binary containing all utils (except stdbuf) by default. To only build a subset `cargo --no-default-features --features <utils>` can be used. Whats missing is building the standalone binaries and a mechanism to automatically disable the build of unix only utils on windows. 2015-07-31 22:49:14 +00:00			`path = "mv.rs"`

			`[dependencies]`
pin dependencies 2017-07-15 19:03:43 +00:00			`getopts = "0.2.14"`
Fix mv build on Windows 2016-11-18 13:58:13 +00:00			`uucore = { path="../uucore" }`
More import fixes for Windows. 2015-12-01 06:27:20 +00:00
use cargo idioms to manage dependency resolution and compilation 2015-11-22 20:45:04 +00:00			`[[bin]]`
Refactor and simplify build for utilities. For coreutils, there are two build artifacts: 1. multicall executable (each utility is a separate static library) 2. individual utilities (still separate library with main wrapper) To avoid namespace collision, each utility crate is defined as "uu_{CMD}". The end user only sees the original utility name. This simplifies build.rs. Also, the thin wrapper for the main() function is no longer contained in the crate. It has been separated into a dedicated file. This was necessary to work around Cargo's need for the crate name attribute to match the name in the respective Cargo.toml. 2015-12-08 02:42:08 +00:00			`name = "mv"`
			`path = "main.rs"`