configure-xcode-for-embedded-development breaks @available in Swift files

• Component: Tools / Tests
• Status: RESOLVED FIXED

[Ali Juma]

The changes applied by configure-xcode-for-embedded-development leave Xcode in state where using @available in a Swift class breaks compilation of Objective-C methods marked with API_AVAILABLE that call into that class.

Specifically, suppose we have:
-a Swift class Foo marked @available(iOS 14.0, *)
-an ObjC class Bar with a method myMethod marked API_AVAILABLE(ios(14))

The changes applied by configure-xcode-for-embedded-development for AvailabilityProhibitedInternal.h cause API_AVAILABLE to be ignored, but @available is not ignored. This means that calling from myMethod into Foo, which should be fine since both are available only in iOS 14+, results in a build failure when building with -Werror -Wunguarded-availability, since after pre-processing, myMethod has no availability notation.

I ran into this when trying to build Chrome for iOS using the same Xcode that I use for building WebKit.

[Ali Juma]

Created attachment 413939 [details]
Patch

[Jonathan Bedard]

Comment on attachment 413939 [details]
Patch

I think this is correct, but I want to verify that our embedded builds still work after this change, which will take some time. Unfortunately, EWS isn't going to test the changes here.

[Jonathan Bedard]

Comment on attachment 413939 [details]
Patch

Tested with out embedded builds, should be good to go!

[Ali Juma]

(In reply to Jonathan Bedard from comment #3)
> Comment on attachment 413939 [details]
> Patch
> 
> Tested with out embedded builds, should be good to go!

Thanks for the review and for testing this!

[EWS]

Committed r269752: <https://trac.webkit.org/changeset/269752>

All reviewed patches have been landed. Closing bug and clearing flags on attachment 413939 [details].

[Radar WebKit Bug Importer]

<rdar://problem/71343631>