We currently add files that aren't in Xcode yet, but we don't remove files that have been renamed or deleted from the Kotlin sourceset.

Adding files to Xcode produces some huge and apparently incorrect relative paths. See tail end of this: https://kotlinlang.slack.com/archives/C3SGXARS6/p1561103800227400

After much research, importing dep sources is not that simple. The binaries are built with references to absolute source paths.

For example, I built sqliter on this machine, so adding those exact source files allows the debugger to work, but adding the same files in a different folder does not. The absolute paths must be in the IR output, and would need a way to be changed.

Possibly change KN compilation and include sources in the klib file.

It's a lot of work and not just in this plugin (unless there's a way to alter the binary and change paths).

Kotlin files are added as compile targets. We can turn that off and only the file to the group, but breakpoints don't work.

Xcode doesn't attempt to compile Kotlin, so it doesn't impact functionality. However, there's a warning.

warning: no rule to process file 'xxx' of type 'text' for architecture 'x86_64' (in target 'yyy')

We should either figure out how to avoid adding files to compile, or a way to disable the error.

If missing 'xcodeproj', run gem install xcodeproj

My work laptop is partially locked and I can't use sudo to install xcodeproj globally. I can however use bundler to install it locally into vendor/bundle. So a workaround for me is to include a Gemfile in my project:

gem 'xcodeproj', '1.7.0'

Install it with bundle install --path vendor/bundle.
And then modify plugin to change ruby build/projimport.rb for bundle exec ruby build/projimport.rb:

...
val scriptArgs = mutableListOf(
        "exec",
        "ruby",
        "build/projimport.rb",
        config.projectPath!!,
        config.target!!,
        config.group,
        File(project.projectDir, "src").path)

    val std = ByteArrayOutputStream()
    val err = ByteArrayOutputStream()
    val result = projectExec(project,
        "bundle",
        null,
        scriptArgs,
        std,
        err
    )
...

Would be good if the plugin could support this, either via a flag in plugin config or by scanning project files to check if a bundler is used.
I could raise a PR if you could advice a preferred way to implement this.

Jetbrains publishes the xcode-compat plugin to ease some setup, including generating an Xcode project and auto-generating a buildForXcode gradle task. You can see it in-use in the AppCode new project templates.

This plugin conflicts with it because they both define an extension named "xcode". As far as I know this means it's impossible to use both on the same project.