CODEWITHSUNDEEP
macosopensslcmakehomebrew
Helmut Januschka
Helmut Januschka

Reputation: 1636

cmake - osx/mac - openssl brew

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 - which throws a a lot 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?

Upvotes: 12

Views: 14803

Answers (6)

Eki
Eki

Reputation: 681

If you have install openssl of specify version by brew, let's say, [email protected], then you can use

brew info [email protected]

and it will tell you all you need to do:

If you need to have [email protected] first in your PATH, run:
  echo 'export PATH="/opt/homebrew/opt/[email protected]/bin:$PATH"' >> ~/.zshrc

For compilers to find [email protected] you may need to set:
  export LDFLAGS="-L/opt/homebrew/opt/[email protected]/lib"
  export CPPFLAGS="-I/opt/homebrew/opt/[email protected]/include"

For pkg-config to find [email protected] you may need to set:
  export PKG_CONFIG_PATH="/opt/homebrew/opt/[email protected]/lib/pkgconfig"

Upvotes: 0

hannes ach
hannes ach

Reputation: 17723

As of late 2021 this works for me:

change to

cmake_minimum_required(VERSION 3.20.2)

and

find_package(OpenSSL REQUIRED)

Upvotes: 0

micolous
micolous

Reputation: 11

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.

Upvotes: 1

Vlad
Vlad

Reputation: 9481

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

Upvotes: 1

Jonatan
Jonatan

Reputation: 3992

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 .

Upvotes: 18

Helmut Januschka
Helmut Januschka

Reputation: 1636

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 :)

Upvotes: 9

Related Questions