Replies: 1 comment 1 reply
-
i could be wrong but some env vars are not forwarded since they might be overwritten by the default env in stable.toml |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
TLDR: Is there a way to call
cargo make
from a task that forwards everything (including env, cli args passed to cargo-make itself)?I have a situation where I have 2 separate workspaces with 2 separate (and different) Makefiles. The 2 workspaces share a common parent directory which has a 3rd makefile. In this 3rd makefile, I would like to have tasks to call the makefiles from the 2 workspaces (ie. subdirectories). I want to do it in a way where the init tasks of the sub-directories are called, the cargo-make setting passed to the parent makefile are forwarded (ex.
cargo make --no-workspace makefile-a-task
will forward--no-workspace
to the makefile a task), and also want all cargo-make configurations forwarded (ex. i wantenv
section in parent makefile to apply to the sub ones). This is what I have so far:This seems to forward
env
, and also run the init tasks forsub-dir
, but it doesn't handle forwarding cargo-make cli args (i.e.cargo make --env RUSTFLAGS="-D warnings" sub-flow
won't applyRUSTFLAGS
tosub-dir-task-name
). Is there a canonical way to handle this?Beta Was this translation helpful? Give feedback.
All reactions