Discovered a way to handle library/include paths w...
# kotlin-native
n
Discovered a way to handle library/include paths without hard coding them in the def file, which only works for a static C library. In the build file include paths are passed to the compilerOpts function, and library paths are passed to the extraOpts function: https://gitlab.com/napperley/jmonitor/-/blob/master/build.gradle.kts#L16
d
I tried that ages ago but it didn't work out for some reason.
I ended up including it in the library KLIB instead of the cinterop KLIB.
n
What was the reason why it didn't work out?
d
The option seemed to be ignored by the compiler. It was probably an issue with relative paths, not sure
n
Interesting. Why are you using relative paths instead of absolute ones?
d
I was using absolute paths (I'm saying maybe I was using relative by accident). I don't why it wasn't working at the time.