You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have you thought about adding support for the cocoapods-pod-linkage plugin? As explained in this post cocoapods only allows to specify one type of linking for all the pods. This is specially a problem when having multiple targets like it is the case with the Unity Xcode project after they changed to use a UnityFramework library. We have this problem when integrating different Ironsource adapters where some of them should use static and some of them should use dynamic linking.
The text was updated successfully, but these errors were encountered:
@sp-miguel-ibero
In general we recommend statically linking firebase libraries.
Can you tell us a bit more about your expected podfile? Is there a factor that causes you to want to dynamically link firebase libraries, or is this a case of wanting to statically link firebase libraries while dynamically linking some other libraries?
Also, depending on the use-case, as a temporary workaround it might be possible to let EDM4U generate podfiles, then disable EDM4U and manually edit the podfiles to the desired state.
AlmostMatt
changed the title
[FR] iOS Resolver support for mixing cocoapods linking
[FR] iOS Resolver support for mixing cocoapods static and dynamic linking
Feb 27, 2023
Feature proposal
Have you thought about adding support for the
cocoapods-pod-linkage
plugin? As explained in this post cocoapods only allows to specify one type of linking for all the pods. This is specially a problem when having multiple targets like it is the case with the Unity Xcode project after they changed to use aUnityFramework
library. We have this problem when integrating different Ironsource adapters where some of them should use static and some of them should use dynamic linking.The text was updated successfully, but these errors were encountered: