Take BoringSSL 00019f2: Add text about build logic to the style guide.

This commit is contained in:
Brian Smith 2018-04-29 08:17:45 -10:00
commit d0d195e0d3

View File

@ -400,3 +400,14 @@ return value patterns in legacy functions.
Document private functions in their `internal.h` header or, if static,
where defined.
## Build logic
BoringSSL is used by many projects with many different build tools.
Reimplementing and maintaining build logic in each downstream build is
cumbersome, so build logic should be avoided where possible. Platform-specific
files should be excluded by wrapping the contents in `#ifdef`s, rather than
computing platform-specific file lists. Generated source files such as perlasm
and `err_data.c` may be used in the standalone CMake build but, for downstream
builds, they should be pre-generated in `generate_build_files.py`.