Cargo CLI parameters added

src/cargo/lib.rs

@@ -113,7 +113,7 @@ pub fn call_main_without_stdin<Flags: Decodable>(
 {
     let docopt = Docopt::new(usage).unwrap()
         .options_first(options_first)
-        .argv(args.iter().map(|s| &s[..]))
+        .argv(args.iter().take_while(|x| *x != "--").map(|s| &s[..]))
         .help(true);
 
     let flags = docopt.decode().map_err(|e| {

src/cargo/ops/cargo_rustc/custom_build.rs

@@ -1,4 +1,5 @@
 use std::collections::{HashMap, BTreeSet, HashSet};
+use std::env;
 use std::fs;
 use std::path::{PathBuf, Path};
 use std::str;
@@ -114,6 +115,10 @@ fn build_work<'a, 'cfg>(cx: &mut Context<'a, 'cfg>, unit: &Unit<'a>)
        .env("RUSTC", &cx.config.rustc()?.path)
        .env("RUSTDOC", &*cx.config.rustdoc()?);
 
+    for arg in env::args_os().skip_while(|x| x != "--").skip(1) {
+        cmd.arg(arg);
+    }
+
     if let Some(links) = unit.pkg.manifest().links() {
         cmd.env("CARGO_MANIFEST_LINKS", links);
     }

src/doc/build-script.md

@@ -35,7 +35,14 @@ the build command works.
 ## Inputs to the Build Script
 
 When the build script is run, there are a number of inputs to the build script,
-all passed in the form of [environment variables][env].
+all passed in the form of [environment variables][env] or as a CLI command prameters.
+
+CLI parameters for the build script can be passed after '--' flag, eg.:
+```bash
+cargo build --release -- --source-dir=/tmp/data -a
+```
+
+Parameters after '--' (--source-dir and -a) will be ignored by cargo and passed to build script. Parameters can be read via std::env::args().
 
 In addition to environment variables, the build script’s current directory is
 the source directory of the build script’s package.