Closed markst closed 1 day ago
@JesusMcCloud
Thanks for the heads-up! I'm really curious for the additional info teased. It sounds really promising!
@markst
I think that getting rid of Package.swift
generation completely is not the right choice.
It would be better to give user ability to override Package.swift
.
Also, this change alone brings new possible corner cases.
What if user will use external dependencies inside his Package.swift
?
We then should be able to link them accordingly during the cinterop
phase.
@ttypic what do you think?
Closing in favour of work I'm doing over here: https://github.com/doublesymmetry/kotlin-spm-plugin/pull/1
This change makes it possible to work in a swift package independently which makes development much easier with Swift native code.
Rather than copying contents and generating
Package.swift
we can open our package in Xcode.app and manage dependencies.Will supply more info.