-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Fix 'linker' input unused
warnings in Explicit Module Builds
#39509
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
@swift-ci please test |
@swift-ci please test Windows platform |
Build failed |
9cd9264
to
86958de
Compare
@swift-ci please test |
Build failed |
86958de
to
50aea2f
Compare
@swift-ci please test |
Build failed |
@swift-ci please test macOS platform |
@swift-ci please test windows platform |
Build failed |
It gets interpreted as just an executable we feed to the linker, since we launch `emit-pcm` actions via `swift-frontend` invocations, not `clang`.
…se-extra-clang-opts` is specified. Instead of *just* passing in `ExtraArgs`, we need to make sure to still form a command-line according to Clang's expectation.
50aea2f
to
aa31794
Compare
@swift-ci please test |
@swift-ci please test Windows platform |
1 similar comment
@swift-ci please test Windows platform |
Use
=
version of-working-directory
flag when passing it to clangUnder some circumstances this prevents the directory argument from being treated as an arbitrary path input.
Omit path to
clang
from PCM build command-lineIt gets interpreted as just an executable we feed to the linker, since we launch
emit-pcm
actions viaswift-frontend
invocations, notclang
.Resolves rdar://83104047