-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Fix documentation warnings building runtime with clang-cl #6238
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 shouldnt be needed. The recent change to the inclusion should silence those, if not, that is a cmake issue that we should report. At that point, we can just push the |
I'll test with an updated branch and respond as appropriate |
Can't reproduce. Closing. Thanks |
I can reproduce this - I assume I was building with MSVC instead of clang accidently. Take a look at the log above. I'm going to reopen this issue |
Can you get the actual compiler invocation? I suspect that we arent passing -isystem for the inclusion. |
This is an extract from the ninja build file - seems like ICU is passed as "-I". I think the problem is that clang-cl doesn't expose "-isystem", so its just included normally
|
Its definitely missing |
I'm fairly sure clang-cl/MSVC don't have a |
@compnerd could we get this tested and merged - basically, the problem is that clang-cl/MSVC don't expose any method of defining an include as a system header, I think. See: http://stackoverflow.com/questions/2541984/how-to-suppress-warnings-in-external-headers-in-visual-c This works around the many, many, many warnings! |
@swift-ci Please smoke test |
ICU uses some forms of deprecated documentation. This causes several hundred warnings building the runtime with clang-cl.
We don't care though, because ICU is external.