What's the best way to generate an .aar file from a multiplatform build.gradle file? My iOS targets generate .framework outputs, but I would now like to wrap my android target jar file in an .aar file. Thanks in advance.

change your jvm target to and android target

Thanks for that Kris! I will read all the 4 parts as I might need to do a fat framework for iOS as well.

not sure what you mean. source code doesn't just disappear.

The folders are still there, but it looks like gradle doesn't recognize the android sourcesets:

that's normal

Ok, I wasn't expecting that. • When I refactored the modules (jvmMain/Test to androidMain/Test) in the Project Pane, it prompted me if I wanted to update the Module or Directory. I tried Module, but it wouldn't let me, saying it couldn't rename a root module (?). So I had to choose Directory. • EDIT: Also, when I look at the .aar filed generated, it contains com.example.android.BuildConfig.class. Where does that come from?

the android gradle plugin. All android artifacts have a BuildConfig

I see. The com.example.android namespace comes from what is in the Android manifest file, right?

<?xml version="1.0" encoding="utf-8"?>
<manifest package="com.example.android" />

So I should probably replace com.example.android by com.mycompany.myproject I guess?

yes

So by default, it looks like the aar files don't contain the Kotlin dependencies (especially the Kotlin version used). Does either of the plugins allow adding such dependencies? Initially I was thinking "pom file", but maybe it isn't the "standard" way to include this in an aar file?

that's what maven is for. otherwise you'll have to build a "fat" aar.

Ok, I'll try building a "fat" aar. Part 5 of your series maybe? 😉

i have no idea how to do that 🙂

Yep. But honestly in my case, since I don't use Android APIs, a "skinny" aar file doesn't buy me much compared to a .jar file if it won't include the Kotlin runtime library or at least the version of Kotlin used. I was planning of using an aar file to include such dependencies, since we don't plan on publishing on Maven.

are you using Android APIs or not?

No. But our client/beta tester/partner on the Android side had suggested that one option to include the dependencies (Kotlin version) was through an aar file. Now these dependencies may be as a pom file or not, this isn't clear to me yet.

just ship a fat jar using the shadow jar plugin

If I go that route (fat jar), do you suggest then me to revert to a jvm target? Or should I keep the android target? Or it doesn't really matter?

an android target is incompatible with a jar output

So it boils down to what it simpler to achieve between a fat aar and a fat jar, basically.

yes and no. i wouldn't create an android target unless you need Android SDK APIs

Fair enough. But there's still a non-zero probability (let's say 25%) that in the mid-future, we need to add some BLE layers, which would require Android SDK APIs. On the other hand, maybe it's a "we'll cross that bridge at that moment" situation since the conversion isn't really complicated.

this is why we have artifact repos/dependency management

Yes, but that means publishing to a maven or jcenter repo.

what do you think gets published 😛

I know that publishing is the preferred/modern way to go, but for some reasons (beyond my control), we simply generate the artifacts on our DevOps and then copied/hosted on our developer website. That's why I was looking to package my SDK, including dependencies, in a practical and standard format. I thought a "standard" aar file was the solution, but apparently not, since it needs to be a "fat" aar. I'll get to Rome eventually. 🙃