Bundling forces with cargo-apk?

[MarijnS95]

Hi! I'm one of the maintainers for android-ndk-rs, and occasionally use cargo-ndk to build a crate for Android that doesn't need the surrounding apk. Unfortunately cargo-ndk doesn't work with the R23 NDK due to an issue that has already been solved in ndk-build. I also couldn't get ANDROID_NDK_ROOT to work, presumably because cargo-ndk only recognizes ANDROID_NDK_HOME.

ndk-build is our crate for cross-compiling native binaries and creating apks, and is exactly focused at being reusable in ie. cargo-ndk. Since we're both pursuing the same goal and doing the exact same thing, would you be open to see if we can unify our projects and relieve/share the maintenance "burden"? I envision to start with simply comparing ndk-build to cargo-ndk and integrate any features that are missing, followed by migrating cargo-ndk over to ndk-build. We can optionally take cargo-ndk into the android-ndk-rs tree being another "frontend" CLI to ndk-build just like cargo-apk, if both parties are open to this.

Looking forward to your opinion!

[bbqsrc]

I envision to start with simply comparing ndk-build to cargo-ndk and integrate any features that are missing, followed by migrating cargo-ndk over to ndk-build.

Sounds good.

We can optionally take cargo-ndk into the android-ndk-rs tree being another "frontend" CLI to ndk-build just like cargo-apk, if both parties are open to this.

I'm not a big fan of monorepos but I am happy to make you a maintainer of this repo if your pull request is good. 😄

[MarijnS95]

We can optionally take cargo-ndk into the android-ndk-rs tree being another "frontend" CLI to ndk-build just like cargo-apk, if both parties are open to this.

I'm not a big fan of monorepos but I am happy to make you a maintainer of this repo if your pull request is good.

Me neither, but it has proven useful for small utilities that share the same underlying crate(s) - it saves a ton of hassle having git references in Cargo.toml and/or submodules that constantly need to be updated in parallel. However, ndk-build is published and intended to be used by external crates as well, and cargo-ndk might be its first external user :)

[bbqsrc]

Rather than let this issue linger open, I'll close it for now. If you choose to make a pull request in the future that implements what was described, that would be great. 🙂