Output folder of the Kotlin compiler in Eclipse

Question

The Jetbrains Kotlin compiler in Eclipse outputs to a hidden folder inside the Eclipse compiler plugin. This hidden folder is then made available through the Eclipse Kotlin classpath container.

In bndtools we need a normal file system folder since bnd can run both from the file system as well as in Eclipse. Since the folder is a linked resource there is no known way to translate it outside Eclipse.

Anybody knows how to tell the Kotlin compiler to just output it in the bin folder?

score 7 · Accepted Answer · edited Mar 28 '16 at 09:55

7

Currently, this is not possible in the Kotlin Eclipse plugin.

To make it possible that Kotlin code can be used from Java, Kotlin plugin produce so-called lightweight class files to this folder. These class files do not contain bodies for methods and they are stored in memory.

Actual class files, that are used to run an application, are being built only before launch and they are produced to the default output folder. For now, we cannot produce class files on each save reasonably fast as there is no incremental compilation in the plugin yet: Feel free to upvote for this issue.

edited Mar 28 '16 at 09:55

itzmebibin

9,199
8
48
62

answered Mar 28 '16 at 09:47

Mikhail Zarechenskiy

291
1
7

Thanks. Any way to trigger this creation of those classes from the outside? – Peter Kriens Mar 30 '16 at 17:06
Unfortunately, this is also not possible for now. – Mikhail Zarechenskiy Apr 04 '16 at 22:14
1

But you can run the application so the class files must already be generated somehow? Is there really no way to capture them? – Peter Kriens Apr 09 '16 at 17:09

score 2 · Answer 2 · answered Jul 20 '16 at 10:51

From the short analysis of the code of Kotlin plugin, it looks like the proper method is KotlinCompiler.compileKotlinFiles. It is being called in two contexts:

KotlinBuilder.build — this is the one called on the project build; it makes a call stack trick (or rather a hack...) to check if being called from the LaunchConfigurationDelegate, and depending on the results, either compiles whole project (via its own private fun compileKotlinFiles), or just makes stubs in memory.
KotlinCompilerUtils.compileWholeProject — this is in fact being called from 1.; nice static method, perfect for abuse until the problem is correctly solved in the plugin. :)

So, I'd use the method from 2. wrapped in a similar way as compileKotlinFiles from file in 1.

Output folder of the Kotlin compiler in Eclipse

2 Answers2

Linked