`RPI='arm-unknown-linux-gnueabihf'`.
This option translates to a --target= option to the ultimate
- command, unless that is a cargo subcommand which would reject
- it. `--arch` and `--target` are simply aliases.
+ command, unless that is a cargo subcommand which we know
+ would reject it. `--arch` and `--target` are simply aliases.
* `-u` | `--cargo-lock-update` | `-U` | `--no-cargo-lock-update`
Default is to add them if we are doing an out-of-tree build,
unless we are doing the dance to update the `Cargo.lock` (see
- above) in which case the only relevant files are to be found in
- the build directory).
+ above) since in that case all the relevant files can be found
+ by cargo in the build directory.
The arguments added are
* `file = false`: disables this feature
* `file = true`: equivalent to `file = "Cargo.lock.example"`
+ (this is the default).
* `file = <some leafname>`
Normally you pass `cargo` as an argument to `nailing-cargo`. But you
can also pass `make` or any other command. You may need to pass
-`--no-cargo-manifest-args` to nailing-cargo.
+`--no-cargo-manifest-args` (aka `-M`) to nailing-cargo, to avoid
+passing options like `--manifest-path` to `make` or whatever.
nailing-cargo passes these environment variables to the build command: