Re: [android-building] Re: Soong confusion

I used to use 'mm -B' to figure out which paths a module would touch when compiling without having to dig into the Makefiles themselves. I'd usually do this to rebuild an test or sample APK I needed for some reason that had already been built, but I didn't know where it was. I *know* I can

Re: [android-building] Re: Soong confusion

Ninja fixes almost all of the incremental build issues because it rebuilds whenever the command line changes, so for example changing LOCAL_CFLAGS in an Android.mk file will rebuild everything that has new cflags. There were a few remaining corner cases that cause incremental build issues,

Re: [android-building] Re: Soong confusion

Colin, are you meaning that incremental builds are fine starting from Oreo or P? I don't have a deep knowledge of all AOSP build structure, but I was thinking that in order to fix incremental build issues al the Makefile shall be converted to Blueprint files...at the moment only a subset of

Re: [android-building] Re: Soong confusion

If I'm integrating a large package (Samba, for example), I go through many clean and (re)build cycles until I get a working result. I would typically use (-B) for that. Is there a ninja way to clean a specific package/target rather than the entire build? Thanks, -John On Tuesday, September

Re: [android-building] Re: Soong confusion

I'm also a long-time pre-8.0 developer who has added many packages and heavily customized the framework. How does one unconditionally make (-B) all targets within a given package using the new build system? Thanks, -John On Tuesday, December 12, 2017 at 2:08:35 PM UTC-8, Colin Cross wrote:

Re: [android-building] Re: Soong confusion

On Mon, Dec 11, 2017 at 1:50 PM, Jacob Abrams wrote: > Hello, > > I would like to voice protest over the AOSP build system switch from Make > to Soong. Make is not a perfect tool but it is well documented and > extremely stable. The introduction of ninja into AOSP was

[android-building] Re: Soong confusion

Hello, I would like to voice protest over the AOSP build system switch from Make to Soong. Make is not a perfect tool but it is well documented and extremely stable. The introduction of ninja into AOSP was seamless and acceptable. However, migrating away from Make to a totally new tool with

[android-building] Re: Soong confusion

Thank you for feedback and request for improving the documentation. As I understand, the primary goals of the new build system were: - reliable incremental builds - module definitions less error-prone - build output more predictable across devices Obviously these goals may result in an