[libswift] Undefine IBAction/IBOutlet ObjC macros when building lib swift #39866
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When we compile libswift with c++-interop enabled, it actually ends up compiling the project as objc++ on Darwin platforms because objc interop is necessarily enabled by default. This causes problems in the libswift bridging header because we try to expand the ObjC IBAction/IBOutlet/IBInspectable macros in inappropriate places.
This change fixes the problem by undefining these macros via
-U
flags passed when building libswift.