Building with sibling folder with cmake won't work if changed template files after building in source

[9fcc]

If mistakenly build in source directory and not in build directory, cmake generates .h files from .h.in. And after compiling in build directory it uses .h files from source directory but not from build directory. I've spent much time to determine the problem. One solution is to deny building in source folder. Another is to generate .h files in the source folder while building in build directory.

[brarcher]

If I understand the issue, it sounds like Check does not properly handle building in or out of the source tree for CMake, is that correct?

There was a bit of work done to get Check to build successfully and correctly both in and out of the source tree for its autoconf builds. However, the same rigor has not been undergone for CMake as the intention for CMake was to enable support for Windows, specifically for Visual Studios and MSVC. All the other systems, including MinGW and Cygwin on Windows, are expected to use autoconf.

This issue would be expected to only hit someone hacking on Check, as opposed to someone who were attempting to build Check for their system and use Check, is that correct?

[9fcc]

To those who develop project and test changes using cmake (and ctest after cmake). If and only if they missed build folder and run cmake in source folder. It's an often issue with developers Usually we just remove some build files from source folder and it works. But this case is more complex.