Reorganize Android build process #53
Comments
|
Yes, that would be nice. What would need to be changed and/or added? |
|
The default layout of the projects would help (external/fdlibm instead of just fdlibm, system/core instead of core). An example of a pared-down repo manifest can be seen at https://android.googlesource.com/accessories/manifest/+/master/default.xml Also pulling the build products from $(android)/out/host/{linux,darwin}-x86/obj/... would be totally awesome, but I'd need to add something to get x86-64 host artifacts build products. |
|
I've updated the directory layout to start: 6400231 |
dparnell
pushed a commit
to dparnell/avian
that referenced
this issue
Dec 24, 2013
Per ReadyTalk#53, Avian should build against a standard AOSP checkout, which means we should look for subprojects in the directories the repo utility would place them.
dicej
added a commit
to dicej/avian
that referenced
this issue
Apr 21, 2014
Per ReadyTalk#53, Avian should build against a standard AOSP checkout, which means we should look for subprojects in the directories the repo utility would place them.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be nice to organize the Android build of Avian so it can plug directly into a checked-out Android tree. This makes it convenient for users with a checked-out Android tree, but is should also make it easier for people that don't have an Android tree.
It can use a smaller repo manifest (e.g., "repo init -u http://...") to avoid the long setup instructions.
The text was updated successfully, but these errors were encountered: