Hi Tim, You can read about plan for supporting iOS here <https://lists.swift.org/pipermail/swift-build-dev/Week-of-Mon-20160815/000613.html> and SwiftPM 4 roadmap here <https://lists.swift.org/pipermail/swift-evolution-announce/2017-January/000307.html>. You can write your package in a way that it can be used with SwiftPM, CocoaPods and Carthage (depending on what all you want to support). This allows using the package with SwiftPM for the command line application and other dependency manager(s) for iOS application.
PS: Check out SwiftPlate <https://github.com/JohnSundell/SwiftPlate> which lets generates a template which can be used to support all dependency managers. I haven't actually used it but it looks good! On Thu, Mar 30, 2017 at 6:30 AM, Tim Dean via swift-users < swift-users@swift.org> wrote: > Hello Swift Users: > > Has the roadmap defined a timeframe for building iOS applications using > the Swift Package Manager? I am working on a handful of modules that will > be shared between a Mac command line utility app and a couple different iOS > apps. I’d like to use SPM for building the shared code as individual > modules, and then to define packages for the command line utility and each > iOS application with dependencies on the shared code modules. > > All code will be Swift-only > > Is the SPM a good options or should I be sticking with CocoaPods or > Carthage? > > Thanks > _______________________________________________ > swift-users mailing list > swift-users@swift.org > https://lists.swift.org/mailman/listinfo/swift-users >
_______________________________________________ swift-users mailing list swift-users@swift.org https://lists.swift.org/mailman/listinfo/swift-users
