Before this change, README was suggesting to replace Envoy repo_mapping
from boringssl to openssl_shared. That solution was working only for
the Envoy repository, but bssl_wrapper was still using openssl as a
dependency.
Because of that, even after re-mapping Envoy to shared OpenSSL, Bazel
was still downloading the OpenSSL tarball and using it for bssl_wrapper.
This change fixes that issue by defining functions in openssl.bzl file.
Both of them define openssl repository. The first one
(openssl_repository) uses the OpenSSL tarball. The second one
(openssl_shared_repository) uses shared OpenSSL library.
WORKSPACE by default calls the openssl_repository function and has a
commented call to the openssl_shared_repository function. If someone
wants to build Envoy with shared OpenSSL, the first function call should
be commented and the second one uncommented.
Before this change, README was suggesting to replace Envoy repo_mapping from
boringssl
toopenssl_shared
. That solution was working only for the Envoy repository, but bssl_wrapper was still usingopenssl
as a dependency.Because of that, even after re-mapping Envoy to shared OpenSSL, Bazel was still downloading the OpenSSL tarball and using it for bssl_wrapper.
This change fixes that issue by defining functions in openssl.bzl file. Both of them define
openssl
repository. The first one (openssl_repository
) uses the OpenSSL tarball. The second one (openssl_shared_repository
) uses shared OpenSSL library.WORKSPACE by default calls the
openssl_repository
function and has a commented call to theopenssl_shared_repository
function. If someone wants to build Envoy with shared OpenSSL, the first function call should be commented and the second one uncommented.Signed-off-by: Michal Rostecki mrostecki@opensuse.org