Google Git
Sign in
boringssl / boringssl / 20b18aef7c1adafbeaed8aa80f9df19530ab8900
commit20b18aef7c1adafbeaed8aa80f9df19530ab8900[log] [tgz]
authorDavid Benjamin <davidben@google.com>Sat Dec 06 10:56:59 2025 -0500
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Sun Dec 07 16:46:56 2025 -0800
tree875e50510be10b57e6c474f98e4705dc27c0eeea
parent098d5baf008ffa6321e2c4a358f5475fcf1fe938 [diff]
infra: Retain CMake toolchain defaults in win*_small builders

Passing CMAKE_C_FLAGS and CMAKE_CXX_FLAGS on the command-line seems to
override CMake's toolchain level defaults including, in particular,
/EHsc on Windows. The lack of /EHsc seems to be causing problems for
https://boringssl-review.googlesource.com/c/boringssl/+/83327 for some
reason.

See below for the default CMake flags on win32 and win64, respectively:
https://logs.chromium.org/logs/boringssl/buildbucket/cr-buildbucket/8696219213217830801/+/u/cmake/stdout
https://logs.chromium.org/logs/boringssl/buildbucket/cr-buildbucket/8696219213217830721/+/u/cmake/stdout

There is probably a better way to do this, so I've left a TODO, but for
now this (hopefully) works.

MSVC lets flags be written /Foo or -Foo. Since the CMake defaults use
/Foo, I've matched them and switched -DOPENSSL_SMALL=1 to
/DOPENSSL_SMALL=1 just so it doesn't look out of place, but it should
not make a difference. /Foo is more canonical for Windows' DOS heritage,
and when in Rome...

Change-Id: I938a84d8479a6be3313b6acf04c561af484af5a2
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/85187
Commit-Queue: Xiangfei Ding <xfding@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
Reviewed-by: Xiangfei Ding <xfding@google.com>
3 files changed
tree: 875e50510be10b57e6c474f98e4705dc27c0eeea
  1. .bcr/
  2. .github/
  3. cmake/
  4. crypto/
  5. decrepit/
  6. docs/
  7. fuzz/
  8. gen/
  9. include/
  10. infra/
  11. pki/
  12. rust/
  13. ssl/
  14. third_party/
  15. tool/
  16. util/
  17. .bazelignore
  18. .bazelrc
  19. .bazelversion
  20. .clang-format
  21. .clang-format-ignore
  22. .gitignore
  23. API-CONVENTIONS.md
  24. AUTHORS
  25. BREAKING-CHANGES.md
  26. BUILD.bazel
  27. build.json
  28. BUILDING.md
  29. CMakeLists.txt
  30. codereview.settings
  31. CONTRIBUTING.md
  32. FUZZING.md
  33. go.mod
  34. go.sum
  35. INCORPORATING.md
  36. LICENSE
  37. MODULE.bazel
  38. MODULE.bazel.lock
  39. PORTING.md
  40. PRESUBMIT.py
  41. PrivacyInfo.xcprivacy
  42. README.md
  43. SANDBOXING.md
  44. STYLE.md
README.md

BoringSSL

BoringSSL is a fork of OpenSSL that is designed to meet Google's needs.

Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability.

Programs ship their own copies of BoringSSL when they use it and we update everything as needed when deciding to make API changes. This allows us to mostly avoid compromises in the name of compatibility. It works for us, but it may not work for you.

BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google's product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily.

Currently BoringSSL is the SSL library in Chrome/Chromium, Android (but it's not part of the NDK) and a number of other apps/programs.

Project links:

To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.

There are other files in this directory which might be helpful: