Gilles Peskine c217f48251 Replace the output file atomically ... When writing the new .data file, first write the new content, then replace the target. This way, there isn't a temporary state in which the file is partially written. This temporary state can be misleading if the build is interrupted. It's annoying if you're watching changes to the output and the changes appear as emptying the file following by the new version appearing. Now interrupted builds don't leave a file that appears to be up to date but isn't, and when watching the output, there's a single transition to the new version. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>		2022-10-04 15:10:00 +02:00
..
data_files
mbedtls_dev	Replace the output file atomically	2022-10-04 15:10:00 +02:00
abi_check.py
apidoc_full.sh
assemble_changelog.py
basic.requirements.txt
bump_version.sh
ci.requirements.txt
code_size_compare.py
config.pl
config.py
driver.requirements.txt
ecc-heap.sh
ecp_comb_table.py
find-mem-leak.cocci
footprint.sh
generate_driver_wrappers.py
generate_errors.pl
generate_features.pl
generate_psa_constants.py
generate_query_config.pl
generate_ssl_debug_helpers.py
generate_visualc_files.pl
maintainer.requirements.txt
make_generated_files.bat
massif_max.pl
memory.sh
min_requirements.py
output_env.sh
rm-calloc-cast.cocci
tmp_ignore_makefiles.sh
windows_msbuild.bat