About circular dependencies, I have found <this he...

# kotlin-native

[natario1]

About circular dependencies, I have found this helpful comment and checked out klib/manifest/depends for my cinterop libs A, B, C.

• Starting from a clean environment, If I call cinteropA , its depends are ok.
• Then I call cinteropB, and I can see that its depends include A ? Why would they do so?
• If I call cinteropC, it will be set to depend on A and B... 😄
Now I can definitely see the circular dependencies, but they come from the plugin - not me. How can I workaround this problem? @Artyom Degtyarev [JB]

It even breaks with a single cinterop library.
• Clean env, call cinterop task, depends are OK
• Call cinterop task again, depends now include the lib itself!
• Call cinterop task again, circular dependency detected.