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

Apply new fingerprinting to build dir outputs #3310

Merged
merged 2 commits into from
Dec 2, 2016

Conversation

alexcrichton
Copy link
Member

We now much more aggressively cache the output of the compiler based on feature
sets and profile configuration. Unfortunately we forgot to extend this caching
to build script output directories as well so this commit ensures that build
script outputs are cached the same way with a directory per configuration of
features and output settings.

Closes #3302

@rust-highfive
Copy link

r? @brson

(rust_highfive has picked a reviewer for you, use r? to override)

Remove generation all the way in manifest-parsing and defer it until we actually
need it during compilation. Additionally remove lots of weird logic that's no
longer necessary that we're hashing quite a few fields.
We now much more aggressively cache the output of the compiler based on feature
sets and profile configuration. Unfortunately we forgot to extend this caching
to build script output directories as well so this commit ensures that build
script outputs are cached the same way with a directory per configuration of
features and output settings.

Closes rust-lang#3302
@brson
Copy link
Contributor

brson commented Dec 1, 2016

@bors r+

@bors
Copy link
Collaborator

bors commented Dec 1, 2016

📌 Commit 41579ba has been approved by brson

@bors
Copy link
Collaborator

bors commented Dec 2, 2016

⌛ Testing commit 41579ba with merge c82fd7f...

bors added a commit that referenced this pull request Dec 2, 2016
Apply new fingerprinting to build dir outputs

We now much more aggressively cache the output of the compiler based on feature
sets and profile configuration. Unfortunately we forgot to extend this caching
to build script output directories as well so this commit ensures that build
script outputs are cached the same way with a directory per configuration of
features and output settings.

Closes #3302
@bors
Copy link
Collaborator

bors commented Dec 2, 2016

☀️ Test successful - status-appveyor, status-travis
Approved by: brson
Pushing c82fd7f to master...

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.

different feature sets use the same output directory ($OUT_DIR)
5 participants