Enable incremental caching for faster builds #227
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dioxus has a pretty huge mono-repo and incremental builds would significantly help speed our CI times up.
This PR implements the strategy ideated in #43 that saves and restores the mtimes for the incremental directory per profile, allowing rustc to re-use the incremental objects.
I have yet to implement a sweep-type solution here, but it seems that cargo does some cleaning of the incremental dir itself so the size shouldn't grow out of control.
I wouldn't merge this until we have a sweep-type solution, but I'm opening this to be able to run tests against the dioxus doc site and mono-repo.