This is a proposal to change the NativeBinary.setupTask function visibility. Changing the visibility of this function will enable the possibility to call it from other build processes outside.

Now it is not possible to use the setupFramework function for some cases since it will automatically find a target and use it, not enabling the possibility to use your own configured target.

This plugin currently automates one piece of common boilerplate by generating a gradle task to copy generated frameworks to xcode. Another piece of common boilerplate in Kotlin/Native iOS projects is an iosTest task, which looks something like

task iosTest(dependsOn: 'linkDebugTestIosX64') {
    doLast {
        def testBinaryPath = kotlin.targets.iosSim.binaries.getTest('DEBUG').outputFile.absolutePath
        exec {
            commandLine 'xcrun', 'simctl', 'spawn', "iPhone Xʀ", testBinaryPath
        }
    }
}

Could this task also be generated by the plugin?

Right now it is hard to attach a K/N Framework into Xcode. Wizards to help, but probably are not enough. The idea is to create a task for the plugin. One calls it with the sourceSet name (of Kotlin/Native Framework) and the path to Xcode project. The task patches Xcode project to include the Framework. The implementation may decide automatically to use CocoaPods integration or not.

I see the following from my own behavior:

• I trust Xcode (only) to create a new iOS project (too many things that my go wrong)
• I have a K/N project with the code to re-use
• I want to try it (it should be a one-click action, not a struggle as of now)
• I'm fine using Xcode and IntelliJ for that (my goal is to reuse code, not to try yet another IDE losing the flow)

It is possible to run Gradle in IntelliJ with one JRE while having the other one as default JRE on the system. Different JREs will make Gradle start several different Gradle wrappers.

It will be better to use the same JRE as it was from IntelliJ/AndroidStudio via generating a dedicated script that is used from Xcode build

By default, the plugin uses Xcode environment variable to create the framework. It is hard-to-impossible to add such framework to Xcode project manually, because

• "CONFIGURATION_BUILD_DIR" may point to sandbox folder
• "CONFIGURATION_BUILD_DIR" may contain build target name (thus hardcoding it to Xcode project is not intended)

Let's add an option to store frameworks under Gradle's buildDir folder instead

Running the command: $ ./gradlew consumer

Yields the following output:

Task :plugin FAILED

FAILURE: Build failed with an exception.

• What went wrong: Project directory '/XXX/kotlin-xcode-compat/plugin' is not part of the build defined by settings file '/XXX/kotlin-xcode-compat/settings.gradle.kts'. If this is an unrelated build, it must have it's own settings file.