We tried to make reading files from Soong difficult to do, since this is
very error prone, as shown by this thread. It looks like you may have
bypassed these protections by running very early during initialization.
>
> Also I think that go files are executed only in the clean build not in
>
Thanks Dan for the response. Yes we are using a custom json file to
maintain compiler flags and this json file is parsed in
build/soong/cc/config/global.go file.
I tried adding a Android.bp file to create a module with json file as src
file and added this module as dependency in Android.bp
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.
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.
