Right now, we produce library files in a single rustJniLibs directory, with subdirectories for each target. That works just fine, right up until the set of targets changes: in that case, stale library files can (and do!) remain.
This ticket tracks either using per-target subdirectories, and configuring the directories appropriately -- this probably requires https://github.com/ncalexan/rust-android-gradle/issues/29 -- or making the build task clean up stale target outputs in some way.
Clone of https://github.com/ncalexan/rust-android-gradle/issues/35.
Right now, we produce library files in a single rustJniLibs directory, with subdirectories for each target. That works just fine, right up until the set of targets changes: in that case, stale library files can (and do!) remain.
This ticket tracks either using per-target subdirectories, and configuring the directories appropriately -- this probably requires https://github.com/ncalexan/rust-android-gradle/issues/29 -- or making the build task clean up stale target outputs in some way.