C interop build integration support

[leodouglas]

No description provided.

[joffrey-bion]

Hey! I'd like to thank you again for the effort and the reactivity. I'm not using a lot of sugar in my PR comments, so if something sounds harsh or direct at first glance, please read the text while imagining a gentle and polite tone 😄

I haven't finished reviewing by any means, but I figured it was worth doing a first pass quickly.

[joffrey-bion]

Thanks for your updates! Here is another pass. Sorry for the delay, but also let's wait for @Jeffset to be back from vacation (end of January)

[joffrey-bion]

What are the keys in this map used for? If they don't serve any purpose from the user's perspective, I think we should just make this a list.

[leodouglas]

Hey @joffrey-bion, the original idea was to follow the pattern proposed in the Kotlin/Native documentation, where each cinterops declaration has its own alias, for example:

cinterops {
    val libcurl by creating {
        definitionFile.set(project.file("src/nativeInterop/cinterop/libcurl.def"))
        packageName("com.jetbrains.handson.http")
        compilerOpts("-I/path")
        includeDirs.allHeaders("path")
    }
}

cinterop:
  hello:
    defFile: 'src/nativeInterop/cinterop/libcurl.def'

In that model, using a map makes sense to allow identification by name.

That said, since this alias is not currently used anywhere, I agree there’s no practical benefit from the user’s perspective. We can simplify this and switch to a list.

[leodouglas]

Thanks for your updates! Here is another pass. Sorry for the delay, but also let's wait for @Jeffset to be back from vacation (end of January)

Sure, @joffrey-bion, np