Skip to content

Releases: frankois944/spm4Kmp

v0.3.3

06 Feb 10:32
92e8f3b
Compare
Choose a tag to compare

Fix #65

Fixing some weird spm configuration

v0.3.2

04 Feb 15:56
Compare
Choose a tag to compare

Fix

issue #62

v0.3.1

03 Feb 16:42
0.3.1
b377d88
Compare
Choose a tag to compare

Fix

Make the new flags of the 0.3.0 mutables

v0.3.0

03 Feb 14:14
985ae33
Compare
Choose a tag to compare

New

Add linkerOpts and compilerOpts input parameters for each of the products exported to Kotlin, even the bridge.

These flags will be added to the definition file and used by cinterop.

v0.2.0

27 Jan 09:34
Compare
Choose a tag to compare

New

Fix

  • Fix minor issues

Other

  • Code refactoring

v0.1.1

22 Jan 11:00
3ebec6a
Compare
Choose a tag to compare

Fix

  • Some exported dependency didn't have the correct umbrella header set during the cinterop task, now you can access to the ObjC API correctly

Improvement

  • Better sync performance by avoiding building non-modified dependency

v0.1.0 : the MVP

22 Jan 07:44
a80bbf7
Compare
Choose a tag to compare

The MVP

This release is the first one, and I assume, the good one for continuing the project after experimentation about cInterop and SPM repository; it's the correct approach.

So, finally, this plugin does the equivalent of the CocoaPods Plugins but with the capacity to create a bridge between pure Swift and Kotlin. With that, we can integrate external Swift dependency into your Kotlin project, the Swift Import !

Still remains some issues on SPM package integration, so please, make an issue and I will try to fix that.

What's new ?

  • Better compatibility with SPM package
  • Increase performance on sync

v0.0.9

20 Jan 09:37
78c2dba
Compare
Choose a tag to compare

Important

#43 : For compatibility issues with Xcode, when there is at least one dependency inside the configuration, a local package is generated and must be added to your Xcode project.

Before, the package was generated when at least one dependency was exported, but for non-exported dependency, some resources were missing and could cause issues (rejection, crash, etc.).

Note: When updating the plugin configuration, please reset the package cache of your Xcode project to apply the modification.

Fix

#42 : The plugin won't make an error if the Gradle runs on a non-macOS host.

0.0.8

16 Jan 15:29
05671cb
Compare
Choose a tag to compare

0.0.7

13 Jan 17:36
de90ce2
Compare
Choose a tag to compare
  • Fix unwanted generation of the local package when no product is exported