Thread
#multiplatform
    p

    Patrick Jackson

    3 years ago
    Running into a "Cyclic dependency in library graph" error while compiling, even though it does not appear to be a cyclic dep. I have lib A and lib B. Both are published KMP artifacts. B depends on A. My project depends on A & B. The cyclic dep error happens for lib B. Only happens for native. JVM compiles fine. Any ideas?
    Artyom Degtyarev [JB]

    Artyom Degtyarev [JB]

    3 years ago
    p

    Patrick Jackson

    3 years ago
    @Artyom Degtyarev [JB] TY so much. got it working. is there an issue created for this? seems like this will be a common problem
    a

    alexander.gorshenev

    3 years ago
    @Patrick Jackson could you go into some details what has caused the cycle to appear?
    p

    Patrick Jackson

    3 years ago
    Still not 100% sure. Appears that having artifacts with the same prefix and gradle module name will cause this error. For example libs A, B & C all are from org.mycompany and each lib has its own gradle project with a module named 'lib'. The metadata in the manifest file of the klibs leads the compiler in a circular dep path