openssl: add CURL_BORINGSSL_VERSION
to identify BoringSSL
#9113
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
BoringSSL doesn't keep a version number, and doesn't self-identify itself
via any other revision number via its own headers. BoringSSL revision can
be identified by its commit hash. This hash is usually known by the
builder. This patch adds a way to pass this hash to libcurl, so that it
can display in the curl version string:
For example:
CFLAGS=-DCURL_BORINGSSL_VERSION="c239ffd0"
The setting is optional, and if not passed, BoringSSL will appear without
a version number, just like before this patch.