-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[ci][docker] Use sccache everywhere by default #11267
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
Conversation
This adds `/opt/sccache` to the PATH of each of the CI docker images so when cmake looks for a C compiler it will pick up the sccache wrapper by default. This fixes some issues where compiler invocations weren't being run though sccache. With this approach the invoker doesn't need to do anything specific to set up sccache. This will require a follow up PR to update the Docker images and remove some of the sccache logic in `task_build.py`
|
just confirming--we can disable this when doing a local build, correct? what's the mechanism by which we do that? |
|
You can disable it by setting the compiler in the cmake config as usual ( |
|
right, will this make the default tests/scripts/ci.py take up a bunch of disk though by making a local sccache? |
|
we discussed a bit, this is expected to populate |
This adds `/opt/sccache` to the PATH of each of the CI docker images so when cmake looks for a C compiler it will pick up the sccache wrapper by default. This fixes some issues where compiler invocations weren't being run though sccache. With this approach the invoker doesn't need to do anything specific to set up sccache. This will require a follow up PR to update the Docker images and remove some of the sccache logic in `task_build.py` Co-authored-by: driazati <[email protected]>
This adds `/opt/sccache` to the PATH of each of the CI docker images so when cmake looks for a C compiler it will pick up the sccache wrapper by default. This fixes some issues where compiler invocations weren't being run though sccache. With this approach the invoker doesn't need to do anything specific to set up sccache. This will require a follow up PR to update the Docker images and remove some of the sccache logic in `task_build.py` Co-authored-by: driazati <[email protected]>
This adds `/opt/sccache` to the PATH of each of the CI docker images so when cmake looks for a C compiler it will pick up the sccache wrapper by default. This fixes some issues where compiler invocations weren't being run though sccache. With this approach the invoker doesn't need to do anything specific to set up sccache. This will require a follow up PR to update the Docker images and remove some of the sccache logic in `task_build.py` Co-authored-by: driazati <[email protected]>
This adds `/opt/sccache` to the PATH of each of the CI docker images so when cmake looks for a C compiler it will pick up the sccache wrapper by default. This fixes some issues where compiler invocations weren't being run though sccache. With this approach the invoker doesn't need to do anything specific to set up sccache. This will require a follow up PR to update the Docker images and remove some of the sccache logic in `task_build.py` Co-authored-by: driazati <[email protected]>
This adds
/opt/sccacheto the PATH of each of the CI docker images so when cmake looks for a C compiler it will pick up the sccache wrapper by default. This fixes some issues where compiler invocations weren't being run though sccache. With this approach the invoker doesn't need to do anything specific to set up sccache.This will require a follow up PR to update the Docker images and remove some of the sccache logic in
task_build.pycc @Mousius @areusch