Skip to content

Skip CMake configure step when CMakeCache.txt is present in build folder #47

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

Merged
merged 2 commits into from
Jul 20, 2018

Conversation

gferon
Copy link
Contributor

@gferon gferon commented Jul 17, 2018

When configuring big projects, not re-running CMake every time improves
the cargo build user experience.

@alexcrichton
Copy link
Member

Thanks! Could this perhaps be an option on Config? I've had bad luck historically with not rerunning cmake for incremental builds causing very weird issues. Having this as an option definitely makes sense though!

@gferon
Copy link
Contributor Author

gferon commented Jul 18, 2018

Agreed, the ways of CMake are (sometimes) impenetrable.

What would be a good name for such option?

@alexcrichton
Copy link
Member

Maybe something like .cache_configure(true)?

@gferon
Copy link
Contributor Author

gferon commented Jul 18, 2018

Maybe .always_configure(false) where the default is true would be easier to understand?

Anyway, I'll implement it and add the relevant doc, then we can always change it.

@alexcrichton
Copy link
Member

Sounds great!

gferon and others added 2 commits July 19, 2018 17:30
When configuring big projects, not re-running CMake every time improves
the `cargo build` user experience.
@alexcrichton alexcrichton merged commit 2750291 into rust-lang:master Jul 20, 2018
@alexcrichton
Copy link
Member

👍 Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants