You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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?
@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.
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
The text was updated successfully, but these errors were encountered: