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

Feature Request: Support Swift PM #4

Closed
laosb opened this issue Oct 20, 2019 · 6 comments · Fixed by #7
Closed

Feature Request: Support Swift PM #4

laosb opened this issue Oct 20, 2019 · 6 comments · Fixed by #7

Comments

@laosb
Copy link

laosb commented Oct 20, 2019

GEOSwift has already supported Swift PM. Please support it so we can use it more easily.

@macdrevx
Copy link
Member

Hi @laosb, this is definitely something we want to support. There are some challenges to supporting SPM in geos (the library that GEOSwift is built on), but once those are resolved, we can roll out support to GEOSwift and this library too.

GEOSwift currently works with SPM only on macOS and Linux. It does it by linking with a package-manager-provided geos (homebrew and apt). This solution won’t work for iOS and tvOS though, which is why we need to update our geos project to be able to build with SPM.

@macdrevx
Copy link
Member

GEOSwift/geos#11

@macdrevx
Copy link
Member

GEOSwift/GEOSwift#166

@macdrevx
Copy link
Member

@laosb SPM support is now available starting with v 1.2.0

@laosb
Copy link
Author

laosb commented Nov 22, 2019

@macdrevx Just tried adding GEOSwiftMapKit to my Xcode iOS project via Xcode SwiftPM integration, and it failed when I try to run:

dyld: Library not loaded: @rpath/libgeos.dylib
  Referenced from: /private/var/containers/Bundle/Application/[REDACTED]/[REDACTED].app/[REDACTED]
  Reason: image not found
(lldb) 

Versions:

image

Those are figured out by Swift PM itself.

And it works charmingly on simulator, but only leaves such an error on application starting when tested on an actual device.

@macdrevx
Copy link
Member

Thanks @laosb. Let’s start a new issue to track this problem.

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 a pull request may close this issue.

2 participants