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

Include Xcode Project #29

Closed
atomkirk opened this issue Nov 14, 2015 · 6 comments
Closed

Include Xcode Project #29

atomkirk opened this issue Nov 14, 2015 · 6 comments

Comments

@atomkirk
Copy link

If you could be so kind as to include the (or an) Xcode project that will let me include this in my project without CocoaPods, that would be great.

@wkiefer wkiefer self-assigned this Nov 19, 2015
@xeokeri
Copy link

xeokeri commented Nov 27, 2015

@atomkirk The easiest way is to add git submodules for both SwiftyDropbox and AlomaFire to your project.

Drop in the AlomaFire project to your app's workspace and add in the Alomafire.framework to your project's frameworks.

Then, add in the SwiftyDropbox/Source .swift files to your project, including the .h/.m files, except the SwiftyDropbox.h file.

After that, add this line to your bridging header file.

#import "SecurityUtil.h"

The "DropboxUtils.swift" file, you will need to add the following line or else it won't compile correctly. As the file uses UIKit content but doesn't include the correct import.

import UIKit

Then you should be able to do the rest as normal.

@atomkirk
Copy link
Author

I also have a type JSON so i need it in its own module

@xeokeri
Copy link

xeokeri commented Dec 1, 2015

@atomkirk You could create a new Xcode project, create a Cocoa Touch framework, and add the Dropbox code. Including the submodule for AlomaFire and that would allow you to separate it further.

@atomkirk
Copy link
Author

atomkirk commented Dec 1, 2015

That's what I ended up doing https://github.com/spoken-co/SwiftyDropbox , but the point of this issue is that it wouldn't hurt anything or anyone to include it, but it would save a lot of headache for people who don't see the need for cocoapods anymore with touch frameworks

@jpittman
Copy link

jpittman commented Apr 7, 2016

I have to second what @atomkirk is pointing out here. While this issue helps me resolve getting the SDK integrated, it seems a bit short sighted to only support one approach of integration. Between pull requests #44, #68 and @atomkirk's linked repo, seems like you have a good starting point to throw into a branch for those of us to test externally.

Please make this a priority.

@scobbe
Copy link
Contributor

scobbe commented Sep 16, 2016

Added in ab71ab5

@scobbe scobbe closed this as completed Sep 16, 2016
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

No branches or pull requests

5 participants