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
Is your feature request related to a problem? Please describe.
There is a framework xcode project B, which has two different kinds of platform targets, iOS and MacOS. After I added this framework project B into another app xcode project A as a dependency library. You will find out that, the list of the Build Phases -> Link Binary With Libraries, has both two targets which belong xcode proj B, one is for iOS, another is for MacOS. But the aim of this action is to add one compatible framework into current project as a dependency library, and this behavior should be ensure the dependency library must match the major app's target platform type, like iOS only, or MacOS only.
Is your feature request related to a problem? Please describe.
There is a framework xcode project
B
, which has two different kinds of platform targets, iOS and MacOS. After I added this framework projectB
into another app xcode projectA
as a dependency library. You will find out that, the list of theBuild Phases
->Link Binary With Libraries
, has both two targets which belong xcode projB
, one is for iOS, another is for MacOS. But the aim of this action is to add one compatible framework into current project as a dependency library, and this behavior should be ensure the dependency library must match the major app's target platform type, like iOS only, or MacOS only.I think the method below should be refactored.
The text was updated successfully, but these errors were encountered: