# How to blacklist Qt AUTO\* files
**URL:** https://discourse.cmake.org/t/how-to-blacklist-qt-auto-files/2433
**Category:** Usage
**Created:** [December 28, 2020, 6:40pm UTC](https://discourse.cmake.org/t/how-to-blacklist-qt-auto-files/2433 "2020-12-28T18:40:49Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Dakon](https://discourse.cmake.org/u/Dakon)
#### Post date: [December 28, 2020, 6:40pm UTC](https://discourse.cmake.org/t/how-to-blacklist-qt-auto-files/2433/1 "2020-12-28T18:40:49Z")
I use CMAKE\_AUTO\* for several of my Qt projects. However, the files generated
by this cause some unneeded noise that I would like to avoid.
-the files show up in coverage reports, where I don’t want them
-if I set CLANG\_TIDY then these files are also processed, which not only is
unnecessarily slow, it also adds noise because I can’t fix that
-this is especially true also for the moc\_\*.cpp files
I would like to avoid adding these files by hand, especially not to the CTest
exclude list. I fear I have not overlooked something, so this is some new
property that needs to be implemented. Any opinions what this would look like?
Eike
---
### Author:  [@ben.boeckel](https://discourse.cmake.org/u/ben.boeckel)
#### Post date: [December 28, 2020, 8:31pm UTC](https://discourse.cmake.org/t/how-to-blacklist-qt-auto-files/2433/2 "2020-12-28T20:31:56Z")
I’ve not had issues with them when using an out-of-source build (not a build-under-source) since the `.clang-tidy` configuration file is not present. You might be able to configure a “turn everything off” `.clang-tidy` file into your build tree too.
I don’t think you can turn clang-tidy off on a per-source basis since it is only a target property right now. Adding support would mean splitting Ninja’s rules again for different wrapper tools in use.
SMTK does do CTest exclusions for coverage at least: [https://gitlab.kitware.com/cmb/smtk/-/blob/master/CMake/CTestCustom.cmake.in](https://gitlab.kitware.com/cmb/smtk/-/blob/master/CMake/CTestCustom.cmake.in)