Concept:
Kati (https://android.googlesource.com/platform/build/kati/) — Reads Android.mk files —> Generates build.ninja
Blueprint (https://android.googlesource.com/platform/build/blueprint/) — Reads Blueprint files —> Generates build.ninja
Soong (https://android.googlesource.com/platform/build/soong/) — Reads both Android.mk + Blueprint files? —> Generates build.ninja
Blueprint and Soong work together to read Blueprints files and
generate a build.ninja file. Blueprint is a framework to implement
your own build logic in a high level langauge (Go). It reads
Blueprints files and writes build.ninja files, but all the logic to
determine what build rules to put in the build.ninja file is delegated
to custom build logic, which for Android is Soong.
generate a build.ninja file. Blueprint is a framework to implement
your own build logic in a high level langauge (Go). It reads
Blueprints files and writes build.ninja files, but all the logic to
determine what build rules to put in the build.ninja file is delegated
to custom build logic, which for Android is Soong.
So then kati is just a stop-gap to allow Ninja builds while the other two are in progress? It will eventually be irrelevant?
Yes, kati will be removed once we no longer need legacy support for any makefiles.