| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Issue: #18398
|
| |
|
|
|
|
| |
Start with v2 to distinguish it from server-mode v1.
Issue: #18398
|
| |
|
|
|
|
| |
Start with v2 to distinguish it from server-mode v1.
Issue: #18398
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Add support for client-owned *stateful* query files. These allow
clients to request a list of versions of each object kind and get only
the first-listed version that CMake recognizes. Since clients own their
stateful query files they can mutate them over time. As a client
installation is updated it may update the queries that it writes to
build trees to get newer object versions without paying the cost of
continuing to generate older versions.
Issue: #18398
|
| |
|
|
|
|
|
|
| |
Add support for client-owned stateless query files. These allow clients
to *own* requests for major object versions and get all those recognized
by CMake.
Issue: #18398
|
|
|
Add a file-based API that clients may use to get semantic information
about the buildsystem that CMake generates. Clients will write query
files under a designated location in the build tree, and CMake will
write reply files for clients to read.
Start with support for shared stateless query files. These allow
clients to share requests for major object versions and get all those
recognized by CMake. Once any client has written a shared request to a
build tree it will persist. Other clients will not need to overwrite
the request (since it is stateless) and should not remove it either.
For now we add only an undocumented object kind to use for testing the
query and reply infrastructure. Object kinds providing real semantic
information will be added later.
Issue: #18398
|
