A number of small changes to enable a cmake build of bssl-compat to work in the upstream envoyproxy/envoy-build-ubuntu builder image:
The uncomment.sh script now explicitly uses gawk rather than awk so it knows which awk dialect it can use without any surprises.
If OpenSSL is built as an ExternalProject, because it cannot be found installed on the host, then we need to tell the bssl-compat-utests binary where to load libcrypto/ssl.so from by adding their path to the executable's RPATH.
Since the LLVM libraries can be configured & built with or without RTTI and/or exceptions, the compile & link of the prefixer tool needs to accommodte such differences. To achieve this, it now uses the LLVM provided cmake function llvm_update_compile_flags() to add the appropriate rtti and/or exception compilation flags.
The prefixer now makes use of the LLVM_LIBRARY_DIR cmake variable, to locate the system headers (previously fixed to just /usr/lib/clang/...).
A number of small changes to enable a cmake build of bssl-compat to work in the upstream envoyproxy/envoy-build-ubuntu builder image:
The uncomment.sh script now explicitly uses gawk rather than awk so it knows which awk dialect it can use without any surprises.
If OpenSSL is built as an ExternalProject, because it cannot be found installed on the host, then we need to tell the bssl-compat-utests binary where to load libcrypto/ssl.so from by adding their path to the executable's RPATH.
Since the LLVM libraries can be configured & built with or without RTTI and/or exceptions, the compile & link of the prefixer tool needs to accommodte such differences. To achieve this, it now uses the LLVM provided cmake function llvm_update_compile_flags() to add the appropriate rtti and/or exception compilation flags.
The prefixer now makes use of the LLVM_LIBRARY_DIR cmake variable, to locate the system headers (previously fixed to just /usr/lib/clang/...).