Geert Janssens 0cfb40efeb CMake - use configure_file instead of file(COPY ) wherever possible ... file(COPY ) will only trigger when the destination file doesn't exist yet. It won't retrigger on source file changes. configure_file on the other hand will. To avoid unwanted substitution attempts this can be invoked with the COPYONLY keyword. Disadvantage of configure_file is that it will only take one input file where file(COPY ) can operate on a list of files. As such the configure_file statement has to be wrapped in a foreach. A few uses of file(COPY ) can't be replaced as they are setting file permissions. And the one in make_dist has been kept as that always operates on an empty directory, hence copying is guaranteed. The former will monitor the file for updates and copy it again the latter will only copy the file if it doesn't exist in the destination yet		2020-04-19 21:23:22 +02:00
..
acctchrt_common.gnucash-xea	Remove the emacs comments at the end of files	2018-03-14 23:04:00 +01:00
bas_2019_k1.gnucash-xea	L12N:sv_SE: Update account hierarchies according to BAS 2019	2020-01-03 17:06:15 +01:00
bas_2019_k2_grund.gnucash-xea	L12N:sv_SE: Update account hierarchies according to BAS 2019	2020-01-03 17:06:15 +01:00
CMakeLists.txt	CMake - use configure_file instead of file(COPY ) wherever possible	2020-04-19 21:23:22 +02:00