-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
ccache/ninja does not work when switching branches. #49967
Comments
Why is that the expected behavior? |
The expected behavior should be we should have near instantaneous build even when switching branches. |
Hmm, I don’t think make is supposed to use ninja by default unless you set BUIlD_WITH=ninja in the environment. But I think I have been able to use ccache + ninja just fine most of the time unless deps/v8 gets updated (in particular, the headers, because V8 is just structured in a way that any changes to the headers could lead to almost a rebuild) have you checked if deps/v8 is changed when you switch branches? |
Also I think building.md is a bit misleading here - ccache only helps you when switching between branches that aren’t very different from each other and when the differences themselves would not result in a rebuild. If, for example, a header that most files depend on gets changed, ccache cannot help because you just have to rebuild to see the changes to take effect. |
ccache helps in condition like switching between branches back and forth, as the previous compilation results have been cached. I believe the words in the document can be improved. |
ccache improves the build speed significantly only when the branch was built before. Building fresh branches with major changes are not benefited from ccache. PR-URL: #50133 Fixes: #49967 Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Michaël Zasso <[email protected]>
ccache improves the build speed significantly only when the branch was built before. Building fresh branches with major changes are not benefited from ccache. PR-URL: nodejs#50133 Fixes: nodejs#49967 Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Michaël Zasso <[email protected]>
ccache improves the build speed significantly only when the branch was built before. Building fresh branches with major changes are not benefited from ccache. PR-URL: nodejs#50133 Fixes: nodejs#49967 Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Michaël Zasso <[email protected]>
ccache improves the build speed significantly only when the branch was built before. Building fresh branches with major changes are not benefited from ccache. PR-URL: #50133 Fixes: #49967 Reviewed-By: Yagiz Nizipli <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Michaël Zasso <[email protected]>
Version
v21.0.0-pre
Platform
Darwin Siri-Pro.local 21.6.0 Darwin Kernel Version 21.6.0: Wed Aug 10 14:25:27 PDT 2022; root:xnu-8020.141.5~2/RELEASE_X86_64 x86_64
Subsystem
No response
What steps will reproduce the bug?
No response
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior? Why is that the expected behavior?
No response
What do you see instead?
As suggested in the
building.md
, we should have near instantaneous build even when switching branches.However, when I switched the branch in my local, I can see that it restarted the building process for
make
.Additional information
No response
The text was updated successfully, but these errors were encountered: