Issue with Xcode 15's Mergeable Libraries?

Question

filbercio OP

Created Nov ’23

Replies 1

Boosts 0

Participants 1

Hi -

I’m trying to move over my current project from Xcode 14 to Xcode 15 and having some issues with the new Mergeable Libraries feature.

Specifically, Xcode 15.0.1 appears to be taking several of my old Xcode 13 and 14 pre-built Frameworks and merging their binaries into the main executable. But it’s doing this despite all the “Merge” Build Settings being set to NO in my main project. Furthermore, Xcode 15 is only doing this to my older pre-built Frameworks. My project also creates several other Frameworks at build time, but Xcode 15 doesn’t seem to be merging those Frameworks into the main executable.

So I’m confused. Since I'm new to Xcode 15 and Mergeable Libraries, I was wondering: Is this expected behavior in Xcode 15 or should I file a bug? I would think that the Mergeable Libraries system would be opt-in, and I haven’t done anything to activate it.

Thanks.

Boost

Answer 1

filbercio OP

Jan ’24

I just tried this with Xcode 15.2 and a Clean build. The same thing is happening. The frameworks that Xcode compiles and links at project Build time are left untouched. However, all pre-built Frameworks that my app links to get Merged into the app's binary.

While I don't think anything bad is happening because of this, I'd prefer to have complete control over my build chain. Is there any way to disable this behavior?

0