NEAT-project / neat

A New, Evolutive API and Transport-Layer Architecture for the Internet
https://www.neat-project.org/
BSD 3-Clause "New" or "Revised" License
66 stars 19 forks source link

Custom OpenSSL dir doesn't use the correct include path #370

Closed bagder closed 7 years ago

bagder commented 7 years ago

I can specify a custom OpenSSL to build neat with like this:

cmake -DOPENSSL_ROOT_DIR=$HOME/build-openssl

... and cmake will correctly identify that version. But it will not setup the correct include path to use the headers as installed in that custom directory, so it'll instead end up building with the system's default openssl headers.

The work-around for this is to manually provide the -I option on the cmake command line:

cmake -DOPENSSL_ROOT_DIR=$HOME/build-openssl -DCMAKE_C_FLAGS=-I$HOME/build-openssl/include