-
Notifications
You must be signed in to change notification settings - Fork 3
Add ccache detection #71
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I want to give some credit, because this really is a novel and clever solution. I just happen not to prefer it to --ccache-skip, because we can't guarantee that ccache will be in the PATH, especially if its only used during build configuration (this is not made up, its a legitimate usecase). Can we not just do that, and keep it in tools.bzl?
e963809 to
02e217b
Compare
|
I have tried my best to reproduce the behaviour you describe. Since we cannot use custom flags, I have resorted to using environment variables. I have decided to pass the CCACHE_DISABLE=1 flag to the jobs. Please test if it works on your machine! |
02e217b to
56c9a9d
Compare
3eac5bc to
c81d553
Compare
This reverts commit c430ce5.
c81d553 to
581e572
Compare
Why:
Bazel and ccache don't work well together. We should warn the user that their analyzers use ccache and fail the job to force the user to disable ccache (by changing package_layout.json or uninstalling ccache)
What:
Extended the repository rule that detects CodeChecker to also detect ccache
Addresses:
Fixes #36