Fix a bug when a local podspec is used by multiple targets with different platforms #710

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
2 participants
@etodd

etodd commented Dec 28, 2012

Here's what happened:

  1. Created a Podfile with two targets, the default one (iOS) and another exclusive one (OS X 10.7).
  2. Both targets reference a local podspec that requires different frameworks to be linked for iOS and OS X (the source code itself is not necessarily local).
  3. CocoaPods generates separate xcconfig files for each target, but the frameworks are the same in both files. (In my case, they both had the OS X frameworks)

This change fixed the issue for me. Probably not the most elegant way to solve the problem, but probably the easiest and least likely to break anything.

@fabiopelosin

This comment has been minimized.

Show comment Hide comment
@fabiopelosin

fabiopelosin Jan 7, 2013

Owner

Although the fix is good I'm not pulling this in because the issue that you are experiencing is just the tip of bigger icerberg related to issues using the same pod for multiple architectures and this implementation has been substantially changed in the 0.17 branch.

Thanks for the submission anyway. The issue should be fixed in the next release.

Owner

fabiopelosin commented Jan 7, 2013

Although the fix is good I'm not pulling this in because the issue that you are experiencing is just the tip of bigger icerberg related to issues using the same pod for multiple architectures and this implementation has been substantially changed in the 0.17 branch.

Thanks for the submission anyway. The issue should be fixed in the next release.

jzapater pushed a commit to jzapater/CocoaPods that referenced this pull request Sep 17, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment