Instead of dynamically globbing the sources, which is fine for a small project, but troublesome for a big project, we should :
check if there is a CMakeLists.txt in the source folder
if there isnt we can generate it by globbing ( good for small projects )
if there is, then we can just include||add_subdirectory it to use it.
This way an upper build chain can generate the sourcelist cmakelists.txt file, and cmake will rerun automatically when detecting a change, and keeping the cached values.
In the case of small projects, cmake will autogenerate its own sourcelist CMakelists.txt. Therefore the behavior will be the same as before for the first run.
The manual step of adding a file will have to be manual... unless we find way to detect a change in the directory contents.. ( signature of filenames or so... )
Instead of dynamically globbing the sources, which is fine for a small project, but troublesome for a big project, we should :
This way an upper build chain can generate the sourcelist cmakelists.txt file, and cmake will rerun automatically when detecting a change, and keeping the cached values.
In the case of small projects, cmake will autogenerate its own sourcelist CMakelists.txt. Therefore the behavior will be the same as before for the first run. The manual step of adding a file will have to be manual... unless we find way to detect a change in the directory contents.. ( signature of filenames or so... )