azalea/kotlin-fork
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add very basic documentation for interop with Swift/Objective-C (#1482)

Browse Source
This commit is contained in:
SvyatoslavScherbina
2018-04-18 20:46:50 +03:00
committed by GitHub
parent 8371ac137f
commit f27d4452f4
3 changed files with 231 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
GRADLE_PLUGIN.md
+6 -2
View File
@@ -328,7 +328,9 @@ The plugin also edits the default `build` and `clean` tasks so that the first on
Kotlin/Native supports building artifacts to be used by other native languages. There are two types of such artifacts:
Objective-C framework and dynamic library.
* **Dynamic library.** A dynamic library may be built using the `dynamic` artifact block. This block contains the same
### Dynamic library
A dynamic library may be built using the `dynamic` artifact block. This block contains the same
options as other ones (except `interop`) allowing one to specify source files, compiler options and libraries used.
Each task building a dynamic library produces two files: the library itself (a `*.so`/`*.dylib`/`*.dll` file depending
on the target platform) and a C language header. Both of them may be accessed via properties of a building task
@@ -345,7 +347,9 @@ on the target platform) and a C language header. Both of them may be accessed vi
```
Using a dynamic library is shown in the [python extension sample](samples/python_extension).
* **Framework.** An Objective-C framework can be built using the `framework` artifact block. This block contains the
### Framework
An Objective-C framework can be built using the `framework` artifact block. This block contains the
same options as other ones. One may access the framework built using `artifact` property of the building task
(see the [**Tasks**](#Tasks) section). Unlike other artifacts this property points to a directory instead of a regular file.