Lines Matching full:boringssl

1 # Incorporating BoringSSL into a project
4 [main README](/README.md) about the purpose of BoringSSL.
9 BoringSSL as an external repository by using a commit from the
16         name = "boringssl",
18         remote = "https://boringssl.googlesource.com/boringssl",
26 Typically projects create a `third_party/boringssl` directory to put
27 BoringSSL-specific files into. The source code of BoringSSL itself goes into
28 `third_party/boringssl/src`, either by copying or as a
31 It's generally a mistake to put BoringSSL's source code into
32 `third_party/boringssl` directly because pre-built files and custom build files
33 need to go somewhere and merging these with the BoringSSL source code makes
38 BoringSSL is designed to work with many different build systems. Currently,
42 build BoringSSL, without too much pain.
45 automatically generate the intermediate files that BoringSSL needs. However,
51 expects to be run from the `third_party/boringssl` directory and to find the
52 BoringSSL source code in `src/`. You should pass it a single argument: the name
62 [file](https://code.google.com/p/chromium/codesearch#chromium/src/third_party/boringssl/BUILD.gener…
64 [test](https://code.google.com/p/chromium/codesearch#chromium/src/third_party/boringssl/BUILD.gener…
68 files. Periodically an engineer updates the BoringSSL revision, regenerates
70 done [in Chromium](https://code.google.com/p/chromium/codesearch#chromium/src/third_party/boringssl…
74 BoringSSL does not present a lot of configurability in order to reduce the
90 You cannot link multiple versions of BoringSSL or OpenSSL into a single binary
96 objects, ensure you build BoringSSL with `-fvisibility=hidden` and do not
97 export any of BoringSSL's symbols. This will prevent any collisions with other
99 that all callers of BoringSSL APIs live in the same shared object as BoringSSL.
101 If you require that BoringSSL APIs be used across shared object boundaries,
103 `BORINGSSL_SHARED_LIBRARY` in both BoringSSL and consumers. BoringSSL's own
105 `BORINGSSL_IMPLEMENTATION` defined. This will export BoringSSL's public symbols
108 of BoringSSL or OpenSSL.