kc3-lang/libressl
Branch :
Log
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
 |
a67ba9f4 | 2019-04-11 07:28:49 | add pthread_mutex* windows compat for libtls | |
|
41f58606 | 2019-04-11 06:58:58 | include cmake find module in distribution | |
|
89e43070 | 2019-04-11 06:27:01 | Land #503, add CMake module | |
|
7dfda754 | 2019-04-11 06:26:45 | update manpage links | |
|
4b6c7bfd | 2019-03-19 05:39:39 | update links | |
|
6b8dcd5b | 2019-03-19 05:32:58 | Add #506, add SM4 build | |
 |
4ea2a01a | 2019-02-24 15:41:47 | Add ssl/ssl_transcript.c and remove ssl/t1_hash.c | |
 |
23fa9a51 | 2019-03-02 12:32:12 | Add portable scaffold for SM4 | |
 |
3d989bc9 | 2019-02-11 20:54:30 | Readme: Using LibreSSL with a CMake project | |
|
1dd2d050 | 2019-02-11 20:30:17 | Add LibreSSL CMake Find Module CMake has the find_package function which tries to find the library install paths, and if found, gives the user some "interfaces" to use when including the library in their project. There was no LibreSSL module so i wrote one 👍. Placing this file in a new folder called CMake in the same folder as the root CMakeLists.txt file, and adding the following line to the top of it: set(CMAKE_MODULE_PATH "${CMAKE_CURRENT_SOURCE_DIR}/CMake;${CMAKE_MODULE_PATH}") Lets the user run the find_package like so: find_package(LibreSSL REQUIRED) If LibreSSL is installed and found, the user can then just include the library in their target like so: target_link_libraries(test LibreSSL::TLS) They are cascaded, TLS requires and sets SSL, which also requires and sets Crypto using INTERFACE_LINK_LIBRARIES. Instead of setting the CMAKE_MODULE_PATH like above, the file can be placed in the CMake modules folder. For linux CMake will look for LibreSSL in the default install location of "sudo make install", which was on Ubuntu /usr/local/ For Windows the user can set the paths to their library files and include folder manually using the CMake-GUI. |