Local dependencies for cargo-make scripts about cargo-make

[sagiegurari]

by default cargo-make uses rust-script to invoke these. so checkout if its possible to do it there and if not, ask for changes that can be reflected in the script/env.
one thing that might resolve your issue is the RUST_SCRIPT_BASE_PATH env but i'm not sure.

[wmmc88]

Turns out rust-script added --base-path in v0.30.0: fornwall/rust-script#109

[sagiegurari]

closing for now.

[wmmc88]

@JohnScience were you able to find a solution to using local path dependencies with rust-script?

I was recently playing around with this today and RUST_SCRIPT_BASE_PATH is something that rust-script provides as the base path for local dependency resolution, but its not something that the user can modify.

Since rust-script dependencies are doc comments at the top of the script file, there seems like no simple built-in way for someone to modify something like this:

//! ```cargo
//! [dependencies]
//! my-local-crate = { path = "./crates/my-local-crate" }
//! ```

to something like this:

//! ```cargo
//! [dependencies]
//! my-local-crate = { path = "some/absolute/path/based/on/CARGO_MAKE_CURRENT_TASK_INITIAL_MAKEFILE_DIRECTORY /crates/my-local-crate" }
//! ```

Since the dependency is in a doc comment in a script block, it can't expand something like CARGO_MAKE_CURRENT_TASK_INITIAL_MAKEFILE_DIRECTORY or read the environment. Is the best thing to do here to pre-process the script block with a cargo-make plugin?

[JohnScience]

@JohnScience were you able to find a solution to using local path dependencies with rust-script?

I was recently playing around with this today and RUST_SCRIPT_BASE_PATH is something that rust-script provides as the base path for local dependency resolution, but its not something that the user can modify.

Since rust-script dependencies are doc comments at the top of the script file, there seems like no simple built-in way for someone to modify something like this:

//! ```cargo
//! [dependencies]
//! my-local-crate = { path = "./crates/my-local-crate" }
//! ```

to something like this:

//! ```cargo
//! [dependencies]
//! my-local-crate = { path = "some/absolute/path/based/on/CARGO_MAKE_CURRENT_TASK_INITIAL_MAKEFILE_DIRECTORY /crates/my-local-crate" }
//! ```

Since the dependency is in a doc comment in a script block, it can't expand something like CARGO_MAKE_CURRENT_TASK_INITIAL_MAKEFILE_DIRECTORY or read the environment. Is the best thing to do here to pre-process the script block with a cargo-make plugin?

[tasks.ensure_cfg]
script_runner = "@shell"
cwd = "./"
script = '''
cargo run --manifest-path ./cargo-make-scripts/ensure_cfg/Cargo.toml