Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow cocoapods install of Firebase + Geofire for Swift #14

Merged
merged 1 commit into from
May 21, 2015

Conversation

katfang
Copy link
Contributor

@katfang katfang commented May 21, 2015

Turns out Swift threw some compiler errors because we included Firebase/Firebase.h in public header files. Moved them into .m files which makes Swift happy.

@jdimond

@@ -28,7 +28,8 @@

#import <Foundation/Foundation.h>
#import <CoreLocation/CoreLocation.h>
#import <Firebase/Firebase.h>

typedef NSUInteger FirebaseHandle;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't really like the redefinition here, but I guess that's what you get when do you weird stuff like using typedefs...

@jdimond
Copy link
Contributor

jdimond commented May 21, 2015

I can merge as is, however I'm a bit surprised that you can do something like including a library in multiple dependencies in Swift. I'm assuming this has something to do with the fact that Firebase is marked as project-level and not public (see [1]). I wonder if there is a way to let CocoaPods know that it should be marked public...

[1] http://stackoverflow.com/questions/24103169/swift-compiler-error-non-modular-header-inside-framework-module

jdimond added a commit that referenced this pull request May 21, 2015
Allow cocoapods install of Firebase + Geofire for Swift
@jdimond jdimond merged commit d5d83b8 into master May 21, 2015
@jdimond jdimond deleted the pod-cleanup branch May 21, 2015 21:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants