Chiebot-Mirror
/
boringssl
mirror of https://gitee.com/mirrors/boringssl.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
Mirror of BoringSSL (grpc依赖) https://boringssl.googlesource.com/boringssl
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2029 Commits
59 Branches
16 Tags
480 MiB
 
 
 
 
 
 
Tag: Branch: Tree: f94f3ed396
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'f94f3ed396'
${ noResults }
boringssl/gen
David Benjamin b2966323f1
Add missing public header for libpki 		8 months ago
..
bcm Check in pre-generated perlasm and error data files 8 months ago
crypto Correctly sort err_data.c inputs 8 months ago
test_support Check in pre-generated perlasm and error data files 8 months ago
README.md Check in pre-generated perlasm and error data files 8 months ago
sources.cmake Add missing public header for libpki 8 months ago
sources.json Add missing public header for libpki 8 months ago

README.md

Pre-generated files

This directory contains a number of pre-generated build artifacts. To simplify downstream builds, they are checked into the repository, rather than dynamically generated as part of the build.

When developing on BoringSSL, if any inputs to these files are modified, callers must run the following command to update the generated files:

go run ./util/pregenerate

To check that files are up-to-date without updating files, run:

go run ./util/pregenerate -check

This is run on CI to ensure the generated files remain up-to-date.

To speed up local iteration, the tool accepts additional arguments to filter the files generated. For example, if editing aesni-x86_64.pl, this command will only update files with "aesni-x86_64" as a substring.

go run ./util/pregenerate aesni-x86_64

For convenience, all files in this directory, including this README, are managed by the tool. This means the whole directory may be deleted and regenerated from scratch at any time.