This is an outsider's question. I am trying to keep it short. I am used to building in the old way with 'make'. AOSP is using a very strange new build system that it is evidently complex and hard to learn. It is hard to help yourself when things go wrong.
Should not any build system provide a common escape mechanism by providing a shell script that builds all the main targets? In make you normally get this by invoking 'make -n'. You can run the resulting script and investigate problems where commands fail. You can modify the script as you wish and you do not have to use make any more if you do not want to. Can I do the equivalent with AOSP? If not, why not and can we change that? I have seen that is very difficult to do that with gradle, which is what comes with the Android SDK. The situation seems even more difficult with AOSP. As mentioned this is a short version of my question, hoping that people will read it, so I have left out details of what versions of software I am using and what I am trying to do. -- -- You received this message because you are subscribed to the "Android Building" mailing list. To post to this group, send email to android-building@googlegroups.com To unsubscribe from this group, send email to android-building+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-building?hl=en --- You received this message because you are subscribed to the Google Groups "Android Building" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-building+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
