Is there an easy way to clear the cinterop cache without changing the .def file? I just updated my s...

# kotlin-native

[vbsteven]

Is there an easy way to clear the cinterop cache without changing the .def file? I just updated my system and some /usr/include headers have changed but as long as the .def file isn't changed it re-uses the previous generated klib. If I change the .def it regenerates, but if I revert my local .def change, and re-run my generator, cinterop seems to revert back to the old cached version.

[Landry Norris]

A gradle clean ought to fix this.

[vbsteven]

That's what I thought as well, and after a clean my build folders are gone, but the behavior remains

[vbsteven]

I'm a bit puzzled atm by this

[Landry Norris]

That’s odd. Wonder where else it’s caching.

[vbsteven]

or there is another cache involved somewhere

[vbsteven]

might be somewhere in gradle home

[vbsteven]

or konan?

[Landry Norris]

I know ~/.gradle/cache exists. But cleaning that is usually a pretty big deal.

[vbsteven]

yeah indeed, that's the brute force approach but requires me to redownload everything for all projects so I prefer not to

[Adam S]

you could try deleting the contents of KONAN_DATA_DIR https://github.com/JetBrains/kotlin/blob/master/kotlin-native/HACKING.md#compiler-environment-variables

[corneil]

Add the include files as a dependency on klib generation.