You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[tasks.membertask]
script = ["echo hello from member"]
cd member1cargo make workspacetask...Task "workspacetask" not foundexit code 404
Confusing docs:
This allows you to maintaining a single makefile for the entire workspace but having access to those custom tasks in every member crate.
Right. Exactly what I want.
This is only relevant for workspace builds which are triggered in the workspace root.
Flows that start directly in the member crate, must manually extend the workspace level makefile using the extend keyword.
Huh? You just said I could access the workspace-level tasks inside members, and then said they have to start in the workspace root? "using the extend keyword" -- how??
To Reproduce
Try above example.
Error Stack
Task "workspacetask" not foundexit code 404
What I'm trying to do
I want to have a common task, e.g. coverage (no, couldn't override that one either, I want Tarpaulin with HTML, not XML, and in each member, not in the root, so had to set:
[config]
skip_core_tasks = true
to even get overriding that to work, else I got a Invalid task: coverage, contains multiple actions error -- different issue, but aggravates the frustration:
cargo make coverage[cargo-make] INFO - cargo make 0.37.23[cargo-make] INFO - [cargo-make] INFO - Project: api[cargo-make] INFO - Build File: Makefile.toml[cargo-make] INFO - Task: coverage[cargo-make] INFO - Profile: development[cargo-make] ERROR - Invalid task: coverage, contains multiple actions.Task { clear: None, description: Some( "Runs coverage (by default using kcov).", ),...
So I want a [tasks.coverage] in my workspace Makefile.toml that will just run the coverage relative to whatever member crate I'm in, only, without having to re-create that task in every Makefile.toml in every member.
CARGO_MAKE_EXTEND_WORKSPACE_MAKEFILE = true (without or with quotes around "true") has no effect.
What am I doing wrong? Can the docs be made more clear on this?
The text was updated successfully, but these errors were encountered:
CARGO_MAKE_EXTEND_WORKSPACE_MAKEFILE works when you start the build on the workspace dir.
it will run all builds for all members and all members 'see/use' also the workspace level makefile (with member level extension automatically done).
Describe The Bug
I am very confused by the README/docs on how to even achieve this.
Relative to workspace:
/Makefile.toml
:/Cargo.toml
:/member1/Makefile.toml
:Confusing docs:
Right. Exactly what I want.
Huh? You just said I could access the workspace-level tasks inside members, and then said they have to start in the workspace root? "using the extend keyword" -- how??
To Reproduce
Try above example.
Error Stack
What I'm trying to do
I want to have a common task, e.g.
coverage
(no, couldn't override that one either, I want Tarpaulin with HTML, not XML, and in each member, not in the root, so had to set:to even get overriding that to work, else I got a
Invalid task: coverage, contains multiple actions
error -- different issue, but aggravates the frustration:So I want a
[tasks.coverage]
in my workspace Makefile.toml that will just run the coverage relative to whatever member crate I'm in, only, without having to re-create that task in every Makefile.toml in every member.CARGO_MAKE_EXTEND_WORKSPACE_MAKEFILE = true
(without or with quotes around "true") has no effect.What am I doing wrong? Can the docs be made more clear on this?
The text was updated successfully, but these errors were encountered: