Any changes in .mk / .bp files should be producing correct incremental builds -- in general since the ninja migration in Android N, though there have been some bug fixes over the years since for some specific use cases. Bug reports would be useful for any cases that you can reproduce on AOSP.
change C/C++ compiler flags in the build configuration files like .json > I'm unaware of any places where we load compiler flags from json files. If you've made your own changes to the build system or compiler, that may need more changes in the build system to produce correct incremental builds (marking any additional files read as dependencies to wherever they're read). One of the special cases is that we don't actually depend on the clang compiler itself for incremental builds, so if you update it in place, that may not trigger rebuilds. Our compiler updates are in version-specific paths, and the path change will trigger a command line change, and thus proper incremental builds. - Dan On Thu, Aug 3, 2023 at 9:06 AM Vijay Ede <quic_v...@quicinc.com> wrote: > Hi, > I want to check if we have an option to do incremental build after we > change C/C++ compiler flags in the build configuration files like .json, > .mk or .bp. > > Currently i am seeing if we update the compiler flags in the config file > and do incremental build it is not taking the upadated flags. we have to > delete the out/ folder and run full build again for updated flags to affect > and this takes longer build times. > > The context i am looking for this is when we do toolchain version > migration we might have some compiler related errors which might need > update in compiler flags. So instead of doing clean build, i am looking for > a way that rest of the build from the point of error continues with new > flags. > > Thanks > Vijay > > -- > -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/android-building/4f428018-1cd4-4e6f-9897-d29cfe821479n%40googlegroups.com > <https://groups.google.com/d/msgid/android-building/4f428018-1cd4-4e6f-9897-d29cfe821479n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/CALQgHdnFvuNDE7ikBo46O_rO8AoLUusz1vwkfLiXD_rSAcBc7Q%40mail.gmail.com.
