1# Pre-generated files 2 3This directory contains a number of pre-generated build artifacts. To simplify 4downstream builds, they are checked into the repository, rather than dynamically 5generated as part of the build. 6 7When developing on BoringSSL, if any inputs to these files are modified, callers 8must run the following command to update the generated files: 9 10 go run ./util/pregenerate 11 12To check that files are up-to-date without updating files, run: 13 14 go run ./util/pregenerate -check 15 16This is run on CI to ensure the generated files remain up-to-date. 17 18To speed up local iteration, the tool accepts additional arguments to filter the 19files generated. For example, if editing `aesni-x86_64.pl`, this 20command will only update files with "aesni-x86_64" as a substring. 21 22 go run ./util/pregenerate aesni-x86_64 23 24For convenience, all files in this directory, including this README, are managed 25by the tool. This means the whole directory may be deleted and regenerated from 26scratch at any time. 27