Twitter | Search | |
Colin Cornaby
Xcode still can't properly link framework targets to an XCFramework and it's killing me :( You can work around by manually specifying the framework path into the XCFramework. But this breaks Catalyst because it tries to use the Mac slice for Catalyst.
Reply Retweet Like More
Colin Cornaby Feb 11
Replying to @colincornaby
It looks like the problem is that the Xcode build system stages the XCFramework incorrectly. I _think_ the last time I looked at this it was copying the framework out of the XCFramework into the host application's staging directory, and not the framework dependency's staging.
Reply Retweet Like
Colin Cornaby Feb 11
Replying to @colincornaby
Also by link I mean it just doesn't find the framework at all when it goes to compile the framework so I suppose that's pre-link.
Reply Retweet Like
Colin Cornaby Feb 11
Replying to @colincornaby
Wait no that's totally the linker stage I was right
Reply Retweet Like