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
set(CMAKE_DEBUG_POSTFIX"d"CACHESTRING"DEBUG_POSTFIX property is initialized when the target is created to the value of this variable except for executable targets")
6
8
7
9
# Allow to have all executables generated in the same binary directory. Otherwise there would be in a directory different for each add_subdirectory cmake commande.
8
10
set (FETPAPI_BINARY_DIR${CMAKE_CURRENT_BINARY_DIR})
9
11
10
12
# version mechanism
11
13
set (Fetpapi_VERSION_MAJOR 0)
12
-
set (Fetpapi_VERSION_MINOR 1)
14
+
set (Fetpapi_VERSION_MINOR 2)
13
15
set (Fetpapi_VERSION_PATCH 0)
14
16
set (Fetpapi_VERSION_TWEAK 0)
17
+
15
18
set (Fetpapi_VERSION ${Fetpapi_VERSION_MAJOR}.${Fetpapi_VERSION_MINOR}.${Fetpapi_VERSION_PATCH}.${Fetpapi_VERSION_TWEAK})
16
19
20
+
if (CMAKE_INSTALL_PREFIX_INITIALIZED_TO_DEFAULT)
21
+
set (CMAKE_INSTALL_PREFIX${CMAKE_CURRENT_BINARY_DIR}/install CACHEPATH"${PROJECT_NAME} install prefix"FORCE)
Copy file name to clipboardExpand all lines: README.md
+5-9Lines changed: 5 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@
7
7
- dependencies
8
8
- The following compilers are known to work (used in CI)
9
9
- gcc from version 4.8
10
-
- visual studio from version 2017
10
+
- visual studio from version 2019
11
11
# Prepare the dependencies
12
12
Download (build and install if necessary) third party libraries:
13
13
- BOOST : All versions from version 1.66 should be ok but you may experience some [min/max build issues](https://github.com/boostorg/beast/issues/1980) using version 1.72 or 1.73.
@@ -27,10 +27,8 @@ FETPAPI uses cmake as its build tool. A 3.12 version or later of cmake is requir
27
27
- give real path and files to the following cmake variables:
28
28
- BOOST
29
29
- Boost_INCLUDE_DIR : the directory where you can find the directory named "boost" which contain all BOOST headers
30
-
- AVRO
31
-
- AVRO_INCLUDE_DIR : where the "avro" directory containing all AVRO headers is located
32
-
- (ONLY FOR WINDOWS) AVRO_LIBRARY_DEBUG : Optional, only used by Visual studio Debug configuration, the Avro debug library you want to link to.
33
-
- AVRO_LIBRARY_RELEASE : the AVRO system library you want to link to.
30
+
- AVRO (using [our own cmake find module](./cmake/modules/FindAVRO.cmake))
31
+
- (ONLY IF NOT AUTOMATICALLY FOUND) AVRO_ROOT : The path to the folder containing include and lib folders of AVRO
34
32
- Click again on "Configure" button. You should no more have errors so you can now click on "Generate" button.
35
33
- You can now build your solution with your favorite compiler (and linker) using the generated solution in yourPath/fesapiEnv/build/theNameYouWant
36
34
- OPTIONALLY, you can also set the variables WITH_DOTNET_WRAPPING, WITH_PYTHON_WRAPPING to true if you want to also generate wrappers on top of FETPAPI for these two other programming languages. Don't forget to click again on "Configure" button once you changed the value of these two variables.
@@ -40,10 +38,8 @@ FETPAPI uses cmake as its build tool. A 3.12 version or later of cmake is requir
40
38
- OPENSSL_INCLUDE_DIR : the OpenSSL include directory
41
39
- LIB_EAY_RELEASE : the OpenSSL crypto library you want to link with.
42
40
- SSL_EAY_RELEASE : the OpenSSL ssl library you want to link with.
43
-
- OPTIONALLY, for FESAPI (v2.7.0.0 as a minimal version) support (see [here](https://github.com/F2I-Consulting/fesapi) for documentation on how to build fesapi), please enable the WITH_FESAPI variable and set the following variables :
44
-
- FESAPI_INCLUDE_DIR : the directory where the FESAPI headers are located (generally the include subdirectory of the fesapi installation directory).
45
-
- (ONLY FOR WINDOWS) FESAPI_LIBRARY_DEBUG : Optional, only used by Visual studio Debug configuration, the FESAPI debug library you want to link to.
46
-
- FESAPI_LIBRARY_RELEASE : the FESAPI library you want to link to.
41
+
- OPTIONALLY, for FESAPI (v2.7.0.0 as a minimal version) support (see [here](https://github.com/F2I-Consulting/fesapi) for documentation on how to build fesapi), please enable the WITH_FESAPI variable and usually set the following variable :
42
+
- FESAPI_ROOT : The path to the folder containing include and lib folders of FESAPI (using [our own cmake find module](./cmake/modules/FindFESAPI.cmake))
47
43
48
44
Remark : you can choose where FETPAPI will be installed (using "make install" on Linux or by generating the "INSTALL" project on Visual Studio) by setting the cmake variable called CMAKE_INSTALL_PREFIX
0 commit comments