cmake - osx/mac - openssl brew

2020-05-27 05:08发布

i am using the following cmake commands

# Search OpenSSL
find_package(PkgConfig REQUIRED)
pkg_search_module(OPENSSL REQUIRED openssl)

if( OPENSSL_FOUND )

    include_directories(${OPENSSL_INCLUDE_DIRS})
    message(STATUS "Using OpenSSL ${OPENSSL_VERSION}")
else()
    # Error; with REQUIRED, pkg_search_module() will throw an error by it's own
endif()

it works on linux and on Mac - but on mac it uses the osx-shipped libssl - wich throws a alot of deprecation warnings e.g. 'SSL_library_init' is deprecated: first deprecated in OS X 10.7"

using brew i already installed a newer - openssl-offical - libssl - how can i tell the pkg_search_module in cmake to find and use the brew version?

regards

4条回答
唯我独甜
2楼-- · 2020-05-27 05:28

ok got it working :)

brew upgrade openssl
brew link --force openssl
pkg-config --modversion openssl
#1.0.2

removed the cmake build folder and rerun the cmake .. and the above macro now finds the 1.0.2 libssl :)

查看更多
Deceive 欺骗
3楼-- · 2020-05-27 05:29

Jonathan is right. The MacOS system open ssl is considered insecure. Here is what works for me

  1. Install or upgrade openssl via brew

  2. Add these to your CMakefile. Instead of hard coding you might choose to use a command line parameter or environment variable

    include_directories(BEFORE /usr/local/Cellar/openssl/1.0.2p/include) find_library(OPENSSL_LIB ssl PATHS /usr/local/Cellar/openssl/1.0.2p/lib NO_DEFAULT_PATH) find_library(CRYPTO_LIB crypto PATHS /usr/local/Cellar/openssl/1.0.2p/lib NO_DEFAULT_PATH)

To find the OpenSSL directory use the following command:

brew list openssl
查看更多
老娘就宠你
4楼-- · 2020-05-27 05:32

As of late 2016 this works for me:

In CMakeLists.txt:

find_package(openssl REQUIRED)

Run cmake like this:

cmake -DOPENSSL_ROOT_DIR=/usr/local/opt/openssl .
查看更多
爱情/是我丢掉的垃圾
5楼-- · 2020-05-27 05:52

The cause of this issue is a bug in CMake -- it does not use alternate pkg-config paths correctly.

According to the merge request attached to the bug, the fix should be in cmake 3.17.0 (to be released in Feb 2020).

Otherwise, use this work-around. Hard coding it in your CMakeLists.txt will make things bad for people who use MacPorts instead of Homebrew.

查看更多
登录 后发表回答