-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Un-set CMAKE_C_COMPILER_LAUNCHER and CMAKE_CXX_COMPILER_LAUNCHER in s… #23806
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
…tdlib and unittests
@swift-ci test macOS |
1 similar comment
@swift-ci test macOS |
@swift-ci smoke test Linux |
What happens if you use distcc with this instead of sccache? Will distcc work correctly with a just built compiler? |
Yes, it will work fine with distcc. Distcc will fail to find the compiler on remote server and build locally. |
@swift-ci test macOS |
That is unfortunate... That is going to make building with distcc really noisy and also make it hard to diagnose when /real/ distcc failures are happening. Can you add make this conditional on an option (enabled by default of course)? Can you make distcc being selected via build-script set that flag? |
Or even hackier, I guess you could check what the CMAKE_C_COMPILER_LAUNCHER actually is and conditionalize based off that? |
Yes, I was just thinking that. If it contains sscache don’t set it to empty string. |
…HER in stdlib and unittests" This reverts commit a12625c.
… and CMAKE_CXX_COMPILER_LAUNCHER
I will squash and merge. @swift-ci smoke test |
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 am fine with this.
…tdlib and unittests