| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Issue: #23200
|
|
|
|
|
|
|
| |
These provide more detailed information about how the test project was
configured.
Issue: #23200
|
|
|
|
|
|
|
| |
Provide a replacement for `file(APPEND .../CMake{Output,Error}.log)`
that records messages in the configure log.
Issue: #23200
|
| |
|
|
|
|
|
|
|
|
| |
Many `try_compile` and `try_run` calls occur inside check modules
between `message(CHECK_START)` and `message(CHECK_{PASS,FAIL})` pairs.
Add a field to configure log entries to report this context.
Issue: #23200
|
|
|
|
| |
Issue: #23200
|
| |
|
|
|
|
|
|
|
| |
Provide clients with a way to get a known set of configure log event
versions.
Issue: #23200
|
|
|
|
|
|
|
|
| |
In order to support multiple log versions without buffering the
entire log, move versioning to the level of individual events.
Multiple versions of an event may then be logged consecutively.
Issue: #23200
|
|
|
|
|
|
| |
Add configure log events for `try_compile` and `try_run` results.
Issue: #23200
|
|
Add infrastructure for a "configure log". Use YAML for a balance of
machine- and human-readability to records details of configure-time
events in a structured format.
Teach the RunCMake test framework to support matching the configure log.
Issue: #23200
|