You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+12-5Lines changed: 12 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -62,7 +62,7 @@ First create a build directory from the root of the project. In the build direct
62
62
63
63
For compiling with SSL support:
64
64
65
-
- You need to have the openssl installed in your development environment: (i) Add openssl include directory to include directories, (ii) Add openssl library directory to the link directories list (This is the directory named tls. e.g. cpp/Linux_64/hazelcast/lib/tls), (iii) Set the openssl libraries to link.
65
+
- You need to have the openssl (version 1.0.2) installed in your development environment: (i) Add openssl `include` directory to include directories, (ii) Add openssl `library` directory to the link directories list (This is the directory named `tls`. e.g. `cpp/Linux_64/hazelcast/lib/tls`), (iii) Set the openssl libraries to link.
66
66
67
67
- You can provide your openssl installation directory to cmake using the following flags:
68
68
- DHZ_OPENSSL_INCLUDE_DIR="Path to open installation include directory"
@@ -74,6 +74,12 @@ For compiling with SSL support:
74
74
- For Mac OS and Linux, we link with "ssl" and "crypto"
75
75
- For Windows there is an example linkage for 64 bit library and release build: "libeay32MD ssleay32MD libcrypto64MD libSSL64MD".
76
76
77
+
# Tested Platforms
78
+
Our CI tests are run continuously on the following platforms and compilers:
0 commit comments