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

Xcode projects (iOS, watchOS, tvOS, macOS) support #63

Closed
florentmorin opened this issue Jun 14, 2017 · 2 comments
Closed

Xcode projects (iOS, watchOS, tvOS, macOS) support #63

florentmorin opened this issue Jun 14, 2017 · 2 comments

Comments

@florentmorin
Copy link

Hello,

Did you plan to support Xcode projects using Cocoapods or Carthage?
If necessary, I can contribute.

Thanks!

@siemensikkema
Copy link
Member

Unfortunately this will not be possible for the time being, see #40 and #48. I wonder if things would change if we were to switch to LibreSSL (if this is even possible) since that is support by iOS and macOS 10.13. This in turn might conflict with the planned move to the Server APIs project.

I also see a few other problems:

  • Carthage depends on an Xcode project. This conflicts with SPM.
  • all the dependencies would also need to support the same build manager, right?

I'm closing this for now. Please reopen if you have thoughts on how to work around this.

@jogu
Copy link

jogu commented Sep 16, 2018

Apologies for dragging up an old ticket, but having had to just deal with jwt/jwk on iOS it's a real struggle currently if you particular requirements (eg. I needed ES256 support). A solution that allowed vapor JWT to be used even if it required pulling in openssl may well be worthwhile. There is a cocoa pod for openssl ( https://github.com/krzyzanowskim/OpenSSL ) which is allegedly used by over 11,000 apps ( https://cocoapods.org/pods/OpenSSL-Universal ).

That said, I don't know how/when this might conflict with the move to the Server APIs project, and I can't currently answer your question about dependencies.

FWIW, I ended up using cjose, which also meant pulling in openssl and Jansson. In retrospect I probably should have given more serious consideration to a solution based on vapor JWT.

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

3 participants