New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
script_runner_args
not passed to @rust
script_runner
#1025
Comments
i've changed rust runner over the years when some stopped working... the latest (from 3 years back or so) is rust script - https://rust-script.org which seems it doesn't support getting cli args and passing them to the rust process. a workaround would be to use env vars i guess.... |
I want to use I'm not quite sure how I could use env vars to solve the problem here. The |
ah ok got it. I'll check |
@wmmc88 just pushed a fix for that. would love your feedback that it solves your issue. |
@sagiegurari confirmed its working! |
released new version |
Describe The Bug
My rust-script has a path dependency on a crate in my workspace:
This does not work because the relative path will be wrong once cargo-make copies the contents of the script block into a file (which is currently under
OUT_DIR/_cargo_make_temp/persisted_scripts
, but I've noticed this path change before (I think after #968 was fixed). To fix this issue, I would like to usescript_runner_args
to pass--base-path
torust-script
:But based off the output, it looks like the
script_runner_args
arent being passed torust-script
:Sidenote: I'd rather if I could just use
//! my-crate = { path = "${CARGO_MAKE_CURRENT_TASK_INITIAL_MAKEFILE_DIRECTORY}", version = "0.1.10" }
, but it looks like that expansion is not done forscript
blocks whenscript_runner
is@rust
.The text was updated successfully, but these errors were encountered: