It seems that Soong is not meant to work with those .mk files though; its page talks about newer JSON-like "Android.bp" files that supersede the older make-based Android.mk files[1].
The documentation is terrible, it totally unclear whether .bp or .mk files are used. Maybe .bp file are transistional files only. Who knows?
For platform/system/core [1] there is a .bp file (and a .mk file), but for e.g. fastboot (which is part of system/core) [2] there is only a .mk file, while for soong there is a .bp file again [3]
Interesting (just discovered):
After running "repo sync" the directory .repo/projects/build
contains blueprint.git, kati.git, make.git and soong.git. So I
assume there are the tools to start with.
based on Makefile (two others will be ncluded), implemented in C and Go
.travis.yml available, is building the C implementation
build seems to require ninja (according to travis.yml), but makefile does not use it
tests require ruby
.rravix.yml seems to run more tests than test-target
.travis.yml available
build seems to require ninja and go (according to travis.yml)
Seems to include a lot if Makefiles to be included by Makefiles. There is a README. Scanning ofer this I assume, that this is the "meta-make" for building the android platform (commands m, mm, mmm).
[1]
https://android.googlesource.com/platform/system/core/+/android-cts-8.0_r2
[2]
https://android.googlesource.com/platform/system/core/+/android-cts-8.0_r2/fastboot/
[3]
https://android.googlesource.com/platform/build/soong/+/android-cts-8.0_r2
-- Regards Hartmut Goebel | Hartmut Goebel | h.goebel@crazy-compilers.com | | www.crazy-compilers.com | compilers which you thought are impossible |