Workspace support about cargo-make

[sagiegurari]

Totally agree. If you look in the project tab i already have a task there in the todo column to disable this using cli flag so you can decide when to use it or not.
I think that is best solution.
What do you think?

[theduke]

I think both should work simultaneously.

For example, I might want to build and test all crates, create a binary distribution for the main crate and upload it somewhere, or zip the entire workspace and do something with it.

I think I'd prefer this:

main: Makefile.toml

[tasks.a_task_run_on_some_members]
workspace_members = ["crate_a", "crate_b"]

[tasks.a_task_run_on_all_members]
workspace_members = "*"

[tasks.task_in_root]
script = "tar cvzf all.tar.gz *"
dependencies = ["a_task_run_on_all_members"]

I'd prefer explicitly enabling the recursive behaviour.

[sagiegurari]

So you are talking about a flow that runs tasks on workspace level and on members level.
thats a nice flow, and I guess you could do something like this to implement it (once i implement the cli flag today/tommorrow)

#this is the makefile in the workspace level (root crate)
[tasks.composite]
dependencies = ["member_flow", "workspace_flow"]

[tasks.member_flow]
command = "cargo"
args = ["make", "sometask"]

[tasks.workspace_flow]
#some tasks that should run on workspace level

and than run the whole thing by writing:

cargo make --noworkspace composite

Makes sense? very simple to define and use i think, and if someone reads it, it is simple to see what it actually does.
and no need to redefine the members in both makefile.toml and cargo.toml.
what do you think?

[sagiegurari]

Checkout version 0.3.25 with the new --no-workspace cli arg.

workspace support

CLI Options

I hope it provides the needed tools to build the flow you need, if not please tell me what you think is still needed.

[theduke]

@sagiegurari cool stuff.

I'll try it out soon, but I think it suits my purposes.