I’m not aware of any such capability having been developed since then. If you are on a Unix-based platform though, you should be able to use tee and pipe your output through that to get a similar end result. It would have the added benefit of also capturing output from any external_process() call too, not just message() commands.
It’s a good thought - thanks for that - but unfortunately the design goal is to capture all output from the CMake configure process in a log file automatically (i.e. without users having to do anything special) across all platforms so we can’t depend on Unix specific tools.
(Our message() wrapper does the job now, so we do have a solution, but it’s using the discouraged wrap-the-existing-function trick…)