Including UIKit back to fix compilation errors #19
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
This addresses a compilation error for those using COSTouchVisualizer on a swift project.
joeblau
added a commit
that referenced
this pull request
Feb 4, 2015
Including UIKit back to fix compilation errors
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This addresses a compilation error for those using COSTouchVisualizer on a swift project.
Description of the problem:
If the pod is included on an objective C project, UIKit is included on the headers without issues. But when the consumer project is written on swift UIKit is not available on the global header causing COSTouchVisualizerWindow to not build as it can't find Foundation or UIKit.