Skip to content

Conversation

@markst
Copy link
Contributor

@markst markst commented Jun 20, 2024

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.

image

@markst
Copy link
Contributor Author

markst commented Jun 20, 2024

@JesusMcCloud

@JesusMcCloud
Copy link

Thanks for the heads-up! I'm really curious for the additional info teased. It sounds really promising!

@IlyaGulya
Copy link
Collaborator

IlyaGulya commented Jun 28, 2024

@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?

@markst
Copy link
Contributor Author

markst commented Jul 4, 2024

Closing in favour of work I'm doing over here: doublesymmetry/kotlin-spm-plugin#1

@markst markst closed this Jul 4, 2024
@markst
Copy link
Contributor Author

markst commented Jul 10, 2024

@IlyaGulya thought I'd share this which defines a Package.swift at the root of a repo in order to allow development: https://github.com/markst/radioplayer-kt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants