The more I think about this, the more it seems unnecessary. The original thought was to keep the build directory strictly free of .c files, and only stick other build artifacts in there, but that just makes it really confusing because now we have to worry about putting generated .c files in a separate genc directory.
Also, when I showed @sedwards-lab he expressed concern about this making the build directory structure more complicated than it needs to be, and after mulling on this I agree (especially as I'm thinking about how to support out-of-tree builds, toward #12).
The more I think about this, the more it seems unnecessary. The original thought was to keep the build directory strictly free of
.c
files, and only stick other build artifacts in there, but that just makes it really confusing because now we have to worry about putting generated.c
files in a separategenc
directory.Also, when I showed @sedwards-lab he expressed concern about this making the build directory structure more complicated than it needs to be, and after mulling on this I agree (especially as I'm thinking about how to support out-of-tree builds, toward #12).