# Machine readable output (non-trace)?

**URL:** https://discourse.cmake.org/t/machine-readable-output-non-trace/7654
**Category:** Usage
**Created:** [March 10, 2023, 11:25pm UTC](https://discourse.cmake.org/t/machine-readable-output-non-trace/7654 "2023-03-10T23:25:21Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![kfsone](https://discourse.cmake.org/user_avatar/discourse.cmake.org/kfsone/32/1880_2.png) [@kfsone](https://discourse.cmake.org/u/kfsone)
#### Post date: [March 10, 2023, 11:25pm UTC](https://discourse.cmake.org/t/machine-readable-output-non-trace/7654/1 "2023-03-10T23:25:21Z")

</div>

–trace has the lovely --trace-format=json-v1.

Is there something similar for regular cmake output? Having the cmake output in a structured, json form, would be super-useful for embedding cmake results in a larger structured build report.

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.cmake.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.cmake.org/u/ben.boeckel)
#### Post date: [March 11, 2023, 1:20am UTC](https://discourse.cmake.org/t/machine-readable-output-non-trace/7654/2 "2023-03-11T01:20:19Z")

</div>

Not today, no. I suppose SARIF could be output some day, but I don’t know how much work that would end up being.

---

<div class="post-metadata">

### Author: ![craig.scott](https://discourse.cmake.org/user_avatar/discourse.cmake.org/craig.scott/32/20_2.png) [@craig.scott](https://discourse.cmake.org/u/craig.scott)
#### Post date: [March 11, 2023, 9:35pm UTC](https://discourse.cmake.org/t/machine-readable-output-non-trace/7654/3 "2023-03-11T21:35:20Z")

</div>

You might be interested in the following issue discussion which proposes something along the lines of what you’re asking about:

[https://gitlab.kitware.com/cmake/cmake/-/issues/19438](https://gitlab.kitware.com/cmake/cmake/-/issues/19438)