# how does COMMAND\_CONFIG work for other generators?

**URL:** <https://discourse.cmake.org/t/how-does-command-config-work-for-other-generators/4089>\
**Category:** Code\
**Created:** [September 14, 2021, 4:55pm UTC](https://discourse.cmake.org/t/how-does-command-config-work-for-other-generators/4089 "2021-09-14T16:55:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hex](https://discourse.cmake.org/user_avatar/discourse.cmake.org/hex/32/363_2.png) [@hex](https://discourse.cmake.org/u/hex)\
**Post date:** [September 14, 2021, 4:55pm UTC](https://discourse.cmake.org/t/how-does-command-config-work-for-other-generators/4089/1 "2021-09-14T16:55:52Z")

</div>

the documentation has new generator expression [OUTPUT\_CONFIG](https://cmake.org/cmake/help/latest/manual/cmake-generator-expressions.7.html#genex:OUTPUT_CONFIG) and COMMAND\_CONFIG. I am not familiar with Ninja, it seems like it supports configuration files for file-level dependencies. I am mostly interested in this part:

> With other generators, the content of `...` is evaluated normally.

(where `...` is part of `$<OUTPUT_CONFIG:...>`). How does this expression behave for other generators?

---

<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:** [September 18, 2021, 3:03pm UTC](https://discourse.cmake.org/t/how-does-command-config-work-for-other-generators/4089/2 "2021-09-18T15:03:28Z")

</div>

@kyle.edwards