Mergeable Frameworks not Embedded in App Targets about tuist

[iteracticman]

fyi @AlbGarciam

[AlbGarciam]

Based on the thread you added, we should embed the framework? Won't it add a duplicated symbol?

One of the approaches I usually do is moving my resources into a .bundle to distribute it in a separate manner. Thus I won't have any resource in my framework and I can deliver my resources independently.

This is probably a problem if you have storyboards or xibs in your target.

[kwridan]

Thanks for raising this @iteracticman

From a previous thread it looked like merged frameworks were being embedded and there was proposal to prevent that but resources were the reason for not proceeding with that.

#5694 (review)

[iteracticman]

@AlbGarciam

Based on the thread you added, we should embed the framework? Won't it add a duplicated symbol?

Apparently not, according to Quinn from Apple:

When you use a mergeable framework in your app, you still need to embed the framework so that you get all of its resources. However, what gets embedded is a cut down framework, with all the resources but only a stub Mach-O image.

@kwridan thx for the info. I was not aware of this discussion.

I will investigate a little more and try to come up with a PR to fix this, OK?

[AlbGarciam]

Sure!