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

Make ios_system available as a Swift Package #84

Open
BrianChevalier opened this issue Jul 7, 2019 · 4 comments
Open

Make ios_system available as a Swift Package #84

BrianChevalier opened this issue Jul 7, 2019 · 4 comments
Labels
fix committed A fix for this issue has been committed. Will soon be closed.

Comments

@BrianChevalier
Copy link

The Swift Package manager is now available directly in Xcode where package dependencies can be managed by version, and compiled for the appropriate platform. Packages can also specify their own dependencies (useful for python_ios, and libtex) so new developers don't have to manage that complexity. This will make it an even easier drop-in replacement for system() in iOS apps, as well as testing in the simulator and UIKit for Mac apps.

Creating Swift Packages WWDC19 Session

@BrianChevalier
Copy link
Author

I'll be exploring converting ios_system to a Swift Package and adding updates/resources here.

@holzschu holzschu added the fix committed A fix for this issue has been committed. Will soon be closed. label Jan 3, 2021
@kkebo
Copy link

kkebo commented Jan 22, 2021

Isn't this issue already resolved?

@holzschu
Copy link
Owner

holzschu commented Jan 22, 2021

Yes, but PR #109 is related to that as well. It keeps the binary swift package system, but it changes the method of delivery.
Would you have feedback on the PR?

@kkebo
Copy link

kkebo commented Jan 23, 2021

@holzschu His proposal is great. For example, also in a-Shell, you can fetch XCFrameworks with swift package --package-path xcfs resolve and then their paths become relative to the project directory (e.g. $PROJECT_DIR/xcfs/.build/artifacts/xcfs/*.xcframework). That could resolve this issue as well.

In the future, if SwiftPM supports embedded binary framework, you can go back to Xcode's built-in SwiftPM again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fix committed A fix for this issue has been committed. Will soon be closed.
Projects
None yet
Development

No branches or pull requests

3 participants