# clang-tidy + cxx\_modules

**URL:** https://discourse.cmake.org/t/clang-tidy-cxx-modules/7938
**Category:** Usage
**Created:** [April 20, 2023, 9:39am UTC](https://discourse.cmake.org/t/clang-tidy-cxx-modules/7938 "2023-04-20T09:39:35Z")
**Posts on this page:** 1
**Showing post:** 12

<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: [April 24, 2023, 6:42pm UTC](https://discourse.cmake.org/t/clang-tidy-cxx-modules/7938/12 "2023-04-24T18:42:17Z")

</div>

See also discussion here:

> [@How to control the location of the c++20 Binary Module Interface (BMI) output directory?](https://discourse.cmake.org/t/how-to-control-the-location-of-the-c-20-binary-module-interface-bmi-output-directory/7968/4):
>
> This has not been worked on; clang-tidy may need to learn how to read the modmap file clang will use (though it should exist by the time we’re compiling… The fact that it doesn’t work with compile\_commands.json when the @modmap arguments are there tells me that clang-tidy is ignoring something… Certainly not share as they are arch-dependent. I suspect where they go will be a Linux distro discussion in the FHS umbrella, Apple will just decree for itself, and Microsoft will do Windows things. …

---

_[View the full topic](https://discourse.cmake.org/t/clang-tidy-cxx-modules/7938)._