-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
cargo build in a workspaced crate builds workspaces' default members #5932
Comments
Just ran into this today. It seems to technically behave as the docs here specify, but I don't believe this is the desired behavior for real usage. |
While it might technically behave as the docs specify, that means the case when When you go into the subdirectory of a workspaced crate without So when fixing this, it would probably be good to describe this a bit better in the docs as well. |
Turns out this is pretty trivial to fix, and doesn't break any of the existing tests. I need to add a new test, and think about the docs, but I'll try and open a PR this week (@jrobsonchase thanks for reminding me about this issue). |
This is annoying for me. @Nemo157 is there any chance you'll get around to this? If not I could take a stab at it, since it's supposedly easy. |
I have a virtual workspace where I override the
default-members
. I expected this to just set the package that builds when in the root of the virtual workspace, however when I go into one of the members sub-directories I find that it still only builds the default members:The text was updated successfully, but these errors were encountered: