typical project configuration output could look like this:
the sources for these messages may be arbitrary products and modules, so this must scale up when cascading projects (and conversely, still work when only subprojects are built).
this means that there needs to be a central "ouput collection facility". this may be implemented via
QBS-262, and may hook into QBS-60 to get activated when all configure tests have been processed.
the output itself needs to be tagged, so it can be automatically put into sections, hierarchies, and be sorted.