Skip to content
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

Disable the default --all flag when building. #4386

Closed
photex opened this issue Sep 13, 2019 · 3 comments
Closed

Disable the default --all flag when building. #4386

photex opened this issue Sep 13, 2019 · 3 comments
Assignees
Labels
answered Issues that have an answer and don't require additional action from maintainers

Comments

@photex
Copy link

photex commented Sep 13, 2019

Environment

  • 0.2.105.2133-192
  • 1.37.0
  • CLion 2019.2.1
  • Windows 10

Problem description

Building always uses the --all flag even when I've unchecked the option in the Cargo settings.

Steps to reproduce

I have a very large cargo workspace. Some of the components are generally only able to be built in particular circumstances and environments. I use the default-members configuration in the workspace to exclude these.
Unfortunately, IntelliJ-rust seems to only want to run cargo build --all.

@photex
Copy link
Author

photex commented Sep 13, 2019

cargo-still-uses-all

I see the issue that added this option but it apparently has no effect.
#2604

@mchernyavsky
Copy link
Member

Compile all project targets if possible relates to --all-targets option, not --all.

With the new experimental build tool window (#3926), the "Build" action builds only the current selected configuration instead of all targets.
You can enable the build tool window by setting cargo.build.tool.window.enabled variable to false (see Actions > Registry...).

@photex
Copy link
Author

photex commented Sep 13, 2019

Oof. This makes sense. I keep confusing 'targets' and 'projects'. In this case I specifically want to exclude certain projects.

@mchernyavsky mchernyavsky added the answered Issues that have an answer and don't require additional action from maintainers label Sep 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
answered Issues that have an answer and don't require additional action from maintainers
Projects
None yet
Development

No branches or pull requests

2 participants