Currently, when Maneage is being configured, all the outputs of the build process of many programs are printed in the terminal together and it is very hard to see what is being built at every moment. The way I personally work is to open a parallel terminal, go to the project's top directory and run './project --check-config'.

But in some cases (like when building in Docker, or in the Continuous Integration tests of task #15741) this is not possible because we only have one terminal!

While talking with Mohammadreza on task #15741, this solution suddenly occurred to me: we can make a phony target in the two 'basic.mk' and 'high-level.mk's and set that target to call './project --check-config' until the final configuration-completion file is created. This will print the status of the programs that are currently being built in the middle of all the build outputs.

My only worry now is that this will effectively occupy one of the system's threads (and thus slow down the build!). If there was a way that would could run some kind of back-ground job that would activate every N-seconds (without occupying one thread), it would be great!

But anyway, I can't implement right now and it is mostly just cosmetic (we can ultimately search for the final program target files in '.local/version-info' manually), so I thought of leaving this here in case anyone comes up with a solution in the meantime.