Open bamos opened 9 years ago
When you say "package manager", I think of something like dpkg or rpm, and of course Android already has one: the Play Store. If you're talking about a cross-package build system with dependency resolution, then yes, that might be useful. Is jhbuild a good fit?
jhbuild docs: https://developer.gnome.org/jhbuild/3.12/jhbuild.html
From reading the intro, jhbuild looks useful. I'll further look into later, thanks.
Hi @bgilbert @theonewolf and @wenluhu - just brainstorming here. I've been compiling a lot of utility libraries for ARM in addition to the ones in here, such as tune2fs, mknod, and gammaray. Mostly, I can build them fine with the snippet below, but other times a small diff of the original source is required, or I need to link other static ARM libraries. I've been thinking that a simple ARM package manager to build executables and static libraries from the original source would be helpful to run non-standard C programs on Android. The benefit of centralizing this is that people wouldn't have to manually build or chain together dependencies as I've done in https://github.com/cmusatyalab/diamond-android/blob/master/diamond-android-library/jni/build.sh.
Is this a sane idea? Do you all have any thoughts on this?