summaryrefslogtreecommitdiff
path: root/tests/ui/issues/issue-66706.stderr
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2024-04-12 22:27:33 +0000
committerbors <bors@rust-lang.org>2024-04-12 22:27:33 +0000
commit9782770a810a631db7f2cf3e132354352db92c3d (patch)
tree1de7477645a30cc510a7c6d40755f26e584071d6 /tests/ui/issues/issue-66706.stderr
parent79424056b05eaa9563d16dfab9b9a0c8f033f220 (diff)
parentff3f0a34673a22d439864e5d72038f252d6595e5 (diff)
Auto merge of #121430 - madsmtm:mac-catalyst-iOSSupport, r=wesleywiser
Add `/System/iOSSupport` to the library search path on Mac Catalyst On macOS, `/System/iOSSupport` contains iOS frameworks like UIKit, which is the whole idea of Mac Catalyst. To link to these, we need to explicitly tell the linker about the support library stubs provided in the macOS SDK under the same path. Concretely, when building a binary for Mac Catalyst, Xcode passes the following flags to the linker: ``` -iframework /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk/System/iOSSupport/System/Library/Frameworks -L/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX14.2.sdk/System/iOSSupport/usr/lib ``` This is not something that can be disabled (it's enabled as soon as you enable `SUPPORTS_MACCATALYST`), so I think it's pretty safe to say that we don't need an option to turn these off. I've chosen to slightly deviate from what Xcode does and use `-F` instead of `-iframework`, since we don't need to change the header search path, and this way the flags nicely match on all the linkers. From what I could tell by reading Clang sources, there shouldn't be a difference when just running the linker. CC `@BlackHoleFox,` `@shepmaster` (I accidentally let rustbot choose the reviewer).
Diffstat (limited to 'tests/ui/issues/issue-66706.stderr')
0 files changed, 0 insertions, 0 deletions