配置编译项

For each target, default compilations include:

• and test compilations for JVM, JS, and Native targets.
• A per Android build variant, for Android targets.

If you need to compile something other than production code and unit tests, for example, integration or performance tests, you can .

You can configure how artifacts are produced in:

• 所有编译项 in your project at once.
• since one target can have multiple compilations.
• 具体编译项.

See the and compiler options available for all or specific targets.

为一个目标配置编译项

kotlin {
    jvm().compilations.all {
        kotlinOptions {
            sourceMap = true
            metaInfo = true
        }
    }
}

kotlin {
    targets.jvm.compilations.all {
        kotlinOptions {
            sourceMap = true
            metaInfo = true
        }
    }
}

kotlin {
    jvm {
        val main by compilations.getting {
            kotlinOptions {
                jvmTarget = "1.8"
            }
        }
    }
}

创建自定义编译项

If you need to compile something other than production code and unit tests, for example, integration or performance tests, create a custom compilation.

For example, to create a custom compilation for integration tests of the jvm() target, add a new item to the compilations collection.

kotlin {
        compilations.create('integrationTest') {
            defaultSourceSet {
                dependencies {
                    def main = compilations.main
                            // Compile against the main compilation's compile classpath and outputs:
                            implementation(main.compileDependencyFiles + main.output.classesDirs)
                    implementation kotlin('test-junit')
                    /* ... */
                }
            }
            // Create a test task to run the tests produced by this compilation:
            tasks.register('jvmIntegrationTest', Test) {
                // runtime dependencies, and the outputs of this compilation:
                classpath = compileDependencyFiles + runtimeDependencyFiles + output.allOutputs
                // Run only the tests from this compilation's outputs:
                testClassesDirs = output.classesDirs
            }
        }
    }
}

You also need to create a custom compilation in other cases, for example, if you want to combine compilations for different JVM versions in your final artifact, or you have already set up source sets in Gradle and want to migrate to a multiplatform project.

To include Java sources in the compilations of the JVM target, explicitly enable the Java language support for the target:

• When .

  

• In the build script of an existing project.

  kotlin {
      jvm {
          withJava()
      }
  }

  This applies the Gradle java plugin and configures the target to cooperate with it.

The Java source files are placed in the child directories of the Kotlin source roots. For example, the paths are:

The common source sets cannot include Java sources.

Due to current limitations, the Kotlin plugin replaces some tasks configured by the Java plugin:

• The target’s JAR task instead of jar (for example, jvmJar).
• The target’s test task instead of test (for example, jvmTest).
• The resources are processed by the equivalent tasks of the compilations instead of *ProcessResources tasks.

配置与原生语言的互操作

Kotlin provides interoperability with native languages and DSL to configure this for a specific compilation.

A compilation can interact with several native libraries. Configure interoperability in the cinterops block of the compilation with .

kotlin {
    linuxX64 { // Replace with a target you need.
        compilations.main {
            cinterops {
                myInterop {
                    // Def-file describing the native API.
                    defFile project.file("def-file.def")
                    // Package to place the Kotlin API generated.
                    packageName 'org.sample'
                    // Options to be passed to compiler by cinterop tool.
                    compilerOpts '-Ipath/to/headers'
                    // Directories for header search (an eqivalent of the -I<path> compiler option).
                    includeDirs.allHeaders("path1", "path2")
                    // Additional directories to search headers listed in the 'headerFilter' def-file option.
                    // -headerFilterAdditionalSearchPrefix command line option equivalent.
                    includeDirs.headerFilterOnly("path1", "path2")
                    // A shortcut for includeDirs.allHeaders.
                }
                anotherInterop { /* ... */ }
            }
        }
    }
}

The compilations created for an Android target by default are tied to Android build variants: for each build variant, a Kotlin compilation is created under the same name.

Then, for each compiled for each of the variants, a Kotlin source set is created under that source set name prepended by the target name, like the Kotlin source set androidDebug for an Android source set debug and the Kotlin target named android. These Kotlin source sets are added to the variants’ compilations accordingly.

The default source set commonMain is added to each production (application or library) variant’s compilation. The commonTest source set is similarly added to the compilations of unit test and instrumented test variants.

Annotation processing with kapt is also supported, but due to current limitations it requires that the Android target is created before the kapt dependencies are configured, which needs to be done in a top-level dependencies block rather than within Kotlin source set dependencies.

kotlin {
    android { /* ... */ }
}
dependencies {
    kapt("com.my.annotation:processor:1.0.0")
}

源集层次结构的编译项

Kotlin can build a with the dependsOn relation.

If the source set jvmMain depends on a source set commonMain then:

• Whenever jvmMain is compiled for a certain target, commonMain takes part in that compilation as well and is also compiled into the same target binary form, such as JVM class files.
• Sources of jvmMain ‘see’ the declarations of commonMain, including internal declarations, and also see the dependencies of commonMain, even those specified as implementation dependencies.
• jvmMain can contain platform-specific implementations for the of commonMain.
• The resources of commonMain are always processed and copied along with the resources of jvmMain.
• The language settings of jvmMain and commonMain should be consistent.

• jvmMain should set a languageVersion that is greater than or equal to that of commonMain.
• jvmMain should enable all unstable language features that commonMain enables (there’s no such requirement for bugfix features).
• jvmMain should use all experimental annotations that commonMain uses.