[swift-build-dev] [swift-evolution] Swift Package Manager 3.0 Project Status
k at keith.so
Tue Aug 23 20:43:19 CDT 2016
I'm hoping that swiftpm never really has to deal with the complexities of code
signing and related problems like entitlements. But at the bare minimum it would
need to be able to create dynamic frameworks, optionally including resources
such as strings files or xibs, for consumption by your main app target.
I don't think we're too far away from this but that would need to happen first.
I would be happy to use swiftpm more like Carthage than CocoaPods. So as long as
it could create your frameworks and you could set them up in your project one
time this would totally be usable.
On 08/21, Karl wrote:
> > On 18 Aug 2016, at 03:04, Keith Smiley via swift-evolution <swift-evolution at swift.org> wrote:
> > It sounds like we may not get any heads up about any work on that level of
> > integration:
> > https://twitter.com/jckarter/status/766072626624073729
> > Which I guess also brings up the question of whether or not it will be done in
> > public (which might also be unanswerable).
> > --
> > Keith Smiley
> What special things are needed for iOS support? Isn’t it just another cross-compilation target (albeit one requiring code-signing)?
More information about the swift-build-dev