This repository has been archived by the owner on Mar 29, 2018. It is now read-only.
Define iOS module with the same name as OS X, cleanup duplicate files #11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pNre
added a commit
that referenced
this pull request
Jun 20, 2014
Define iOS module with the same name as OS X, cleanup duplicate files
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After I've tried to integrate
ExSwiftas module in my iOS project, I've discovered that iOS-target does not define the module at all. Now both targets define module with the same nameExSwift.Additionally, I made the project to use the same
*.plistfiles for bot OS X and iOS targets and deleted unnecessary duplicates.