Closed scoopr closed 1 month ago
Meh, just as we got the #2257 merged, some Xcode warning exposes that it supports C_COMPILER_LAUNCHER
attribute, which is a lot simpler than the wrapper script
Attention: Patch coverage is 25.00000%
with 3 lines
in your changes missing coverage. Please review.
Project coverage is 40.62%. Comparing base (
0cc0c62
) to head (dc91279
). Report is 81 commits behind head on main.
Files with missing lines | Patch % | Lines |
---|---|---|
src/compiler/gcc.rs | 0.00% | 1 Missing and 1 partial :warning: |
src/compiler/compiler.rs | 50.00% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Aha, but actually now it enables the response file use, so that needs to be disabled, I was a bit hasty on this PR, it needs a bit more work to be correct.
Alright, when using C_COMPILER_LAUNCHER
, instead of wrapper script for CC
, it seems to be passing a bit more flags (as it knows the compiler better), So I added it to passthrough the -ivfstatcache
path. Also noticed a single -x objective-c++-header
from my project, so went ahead and added that as supported too.
I think it is much better like this.
Just a friendly poke, was there any concerns here?
nope, thanks for the ping :)
I happened to stumble upon the
C_COMPILER_LAUNCHER
Xcode attribute, which fits the bill perfectly, so use that instead.