What’s the state of support for the `kotlin.mpp.en...

# multiplatform

[russhwolf]

What’s the state of support for the kotlin.mpp.enableCompatibilityMetadataVariant flag for library authors to avoid compatibility issues with projects that don’t enable heirarchical project support? I see it in the JB libs, but can I use it or should I avoid it?

[Benjamin Charais]

Currently my team is making the conversion to 1.4.20. We have had no issues ignoring that flag. We are dabbling with implementing it at some point, but so far have seen almost 0 difference in our internal flow with and without. We don’t expose our libs to public usage, all internal.

[russhwolf]

NB I’m not asking about kotlin.mpp.enableGranularSourceSetsMetadata=true which is how you enable hierarchical structure support. I’m asking about a second flag which I understand JB uses internally for compatibility purposes, but is otherwise undocumented.

[Benjamin Charais]

Ah, I misunderstood your point, my fault.

[Erik Christensen]

If I recall correctly from past experimentation, that flag is needed to support projects using an HMPP library when they aren't using HMPP themselves. But it's been a while, so would be curious to hear more about it from someone in the know.

There's also the kotlin.native.enableDependencyPropagation=false flag, which is mentioned in the docs, but not used by JB libraries.