Description
What type of bug is this?
Configuration
What subsystems and features are affected?
Build system
What happened?
timescale db: 2.19.3
openssl - 3.5
postgres: 16.4 - openssl supported and on in postgres config.h file.
cmake: 4.0.2
git for windows: 2.49.0
windows 10: 22H2
Get the following error:
cmake .. -G "NMake Makefiles" -DCMAKE_BUILD_TYPE=Release -DREGRESS_CHECKS=OFF ^ -DOPENSSL_ROOT_DIR="C:/OpenSSL" ^ -DOPENSSL_INCLUDE_DIR="C:/OpenSSL/include" ^ -DOPENSSL_CRYPTO_LIBRARY="C:/OpenSSL/lib/VC/x64/MD/libcrypto.lib" ^ -DOPENSSL_SSL_LIBRARY="C:/OpenSSL/lib/VC/x64/MD/libssl.lib" ^ -DOPENSSL_LIBRARIES="C:/OpenSSL/lib/VC/x64/MD/libcrypto.lib;C:/OpenSSL/lib/VC/x64/MD/libssl.lib" ^ -DOPENSSL_USE_STATIC_LIBS=OFF
-- The C compiler identification is MSVC 19.35.32217.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/bin/Hostx86/x86/cl.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- TimescaleDB version 2.19.3. Can be updated from version 2.19.2
-- Build type is Release
-- Install method is 'source'
-- Using compiler MSVC
-- Found Git: C:/Program Files/Git/cmd/git.exe (found version "2.49.0.windows.1")
-- Compiling against PostgreSQL version 16.4 using pg_config 'C:/Program Files/PostgreSQL/16/bin/pg_config.exe'
-- Regress checks and isolation checks disabled
-- Assertion checks are OFF
-- Looking for USE_OPENSSL
-- Looking for USE_OPENSSL - found
-- Could NOT find OpenSSL, try to set the path to OpenSSL root folder in the system variable OPENSSL_ROOT_DIR (missing: OPENSSL_CRYPTO_LIBRARY)
CMake Error at CMakeLists.txt:603 (message):
TimescaleDB requires OpenSSL but it wasn't found. If you want to continue
without OpenSSL, re-run bootstrap with -DUSE_OPENSSL=0
-- Configuring incomplete, errors occurred!
Attaching file after running this command:
cmake .. -G "NMake Makefiles" --trace-expand -DCMAKE_BUILD_TYPE=Release -DREGRESS_CHECKS=OFF [rest of the options...]
TimescaleDB version affected
2.19.3
PostgreSQL version used
16.4
What operating system did you use?
Windows 10 x64 22H2
What installation method did you use?
Source
What platform did you run on?
Not applicable
Relevant log output and stack trace
How can we reproduce the bug?
Commands recorded above.