如何强制CMake目标myrrlib使用指定版本OpenSSL 1.1.1

问题背景 #

Linux环境下的CMake项目需构建多个共享库，其中部分库依赖vcpkg安装的OpenSSL 3.2.0；但名为myrrlib的共享库依赖某厂商专有库，该厂商附带了OpenSSL 1.1.1m的静态库libssl.a和libcrypto.a。项目根目录的CMakeLists.txt通过find_package(OpenSSL REQUIRED)引入vcpkg的OpenSSL版本，导致构建myrrlib共享库时出现符号重复定义的链接错误，而构建静态库则可成功。

当前myrrlib的CMake配置：

cmake_minimum_required(VERSION 3.26)

set(RR_LIB_DIR "external/pakages/rr/lib")   
set(RR_LIB_FILES
        vendorlib1
        vendorlib2
        vendorlib3
        ssl    # libssl.a is provided by the RR library (it is not installed by vcpkg)
        crypto # libcrypto.a is provided by the RR library (it is not installed by vcpkg)
)

add_library(myrrlib SHARED)
set_property(TARGET myrrlib PROPERTY CXX_STANDARD 17)
target_sources(myrrlib PRIVATE "src/myrrlib.cpp" "src/myrrlib.h")
target_include_directories(myrrlib PUBLIC ${RR_INCLUDE_DIR})
target_link_directories(myrrlib PUBLIC ${RR_LIB_DIR})
target_link_libraries(myrrlib PUBLIC ${RR_LIB_FILES})

链接错误示例：

/opt/rh/devtoolset-11/root/usr/libexec/gcc/x86_64-redhat-linux/11/ld: warning: alignment 8 of symbol `bio_lookup_lock' in /root/programs/vcpkg/installed/x64-linux/debug/lib/libcrypto.a(libcrypto-lib-bio_addr.o) is smaller than 32 in /mnt/c/Dev/myproject/external/packages/rr/lib/libcrypto.a(b_addr.o)
/opt/rh/devtoolset-11/root/usr/libexec/gcc/x86_64-redhat-linux/11/ld: /root/programs/vcpkg/installed/x64-linux/debug/lib/libcrypto.a(libcrypto-lib-bio_addr.o): in function `BIO_ADDR_new':
/root/programs/vcpkg/buildtrees/openssl/x64-linux-dbg/../src/nssl-3.2.0-5a1db6e780.clean/crypto/bio/bio_addr.c:53: multiple definition of `BIO_ADDR_new'; /mnt/c/Dev/myproject/external/packages/rr/lib/libcrypto.a(b_addr.o):b_addr.c:(.text+0x0): first defined here
...
collect2: error: ld returned 1 exit status

解决方案 #

1. 隔离myrrlib的OpenSSL依赖 #

根目录的find_package(OpenSSL REQUIRED)会全局暴露vcpkg的OpenSSL变量，导致myrrlib链接时混入高版本库。需要为myrrlib单独配置厂商的OpenSSL路径，避免全局影响。

2. 修改myrrlib的CMake配置 #

直接指定厂商静态库的完整路径，并优先引入厂商的OpenSSL头文件，确保编译和链接时都使用指定版本：

cmake_minimum_required(VERSION 3.26)

# 临时保存全局OpenSSL变量（避免影响后续其他库）
set(OLD_OPENSSL_INCLUDE_DIR ${OPENSSL_INCLUDE_DIR})
set(OLD_OPENSSL_LIBRARIES ${OPENSSL_LIBRARIES})

# 配置厂商专属的OpenSSL路径
set(RR_OPENSSL_INCLUDE_DIR "external/pakages/rr/include") # 替换为厂商OpenSSL头文件实际路径
set(RR_LIB_DIR "external/pakages/rr/lib")   
set(RR_LIB_FILES
        ${RR_LIB_DIR}/libvendorlib1.a
        ${RR_LIB_DIR}/libvendorlib2.a
        ${RR_LIB_DIR}/libvendorlib3.a
        ${RR_LIB_DIR}/libssl.a    # 明确指定厂商静态库，避免CMake匹配vcpkg版本
        ${RR_LIB_DIR}/libcrypto.a # 明确指定厂商静态库
)

add_library(myrrlib SHARED)
set_property(TARGET myrrlib PROPERTY CXX_STANDARD 17)
target_sources(myrrlib PRIVATE "src/myrrlib.cpp" "src/myrrlib.h")

# 优先引入厂商OpenSSL头文件，确保编译时使用正确版本的声明
target_include_directories(myrrlib PUBLIC ${RR_OPENSSL_INCLUDE_DIR} ${RR_INCLUDE_DIR})

# 直接链接完整路径的静态库，无需target_link_directories
target_link_libraries(myrrlib PUBLIC ${RR_LIB_FILES})

# 恢复全局OpenSSL变量，保证其他库正常使用vcpkg版本
set(OPENSSL_INCLUDE_DIR ${OLD_OPENSSL_INCLUDE_DIR})
set(OPENSSL_LIBRARIES ${OLD_OPENSSL_LIBRARIES})

3. 隐藏静态库符号避免全局冲突 #

构建共享库时，可通过链接选项将厂商静态库的符号隐藏在myrrlib内部，防止与其他依赖高版本OpenSSL的库冲突：

# 添加到myrrlib的配置中
target_link_options(myrrlib PRIVATE -Wl,--exclude-libs,ALL)

该选项会标记静态库中的符号为局部，不会导出到共享库的全局符号表，避免后续链接其他库时出现符号冲突。

4. 验证依赖正确性 #

• 构建完成后，用nm -D libmyrrlib.so | grep BIO_ADDR_new查看符号，确认来自厂商的OpenSSL库
• 用ldd libmyrrlib.so检查，不会显示系统或vcpkg的OpenSSL动态库（因为静态链接了厂商的库）

静态库可构建的原因 #

静态库只是目标文件的归档，构建阶段不会执行完整的符号解析和链接，因此即使存在重复符号也不会报错；而共享库构建时需要完成全量链接，链接器会严格检查全局符号的唯一性，因此触发重复定义错误。

内容的提问来源于stack exchange，提问作者shashashamti2008