11# Building and installing HElib
22
33HElib's build, install and regression tests suite have been built and tested on
4- Ubuntu 16.04, Ubuntu 18.04, Ubuntu 20.04, Fedora 31, Fedora 32, CentOS 7.7,
4+ Ubuntu 18.04, Ubuntu 20.04, Fedora 31, Fedora 32, CentOS 7.7,
55CentOS 8.1, and macOS Mojave 10.14.
66
77There are two different ways to build and install HElib. The first one will
@@ -14,13 +14,15 @@ dependencies to be installed by you and available in the system.
1414
1515## General prerequisites
1616
17- - cmake >= 3.5.1
17+ - cmake >= 3.10.2 ( * )
1818- GNU make >= 3.82
19- - g++ >= 5.4.0 (for Linux environments)
19+ - g++ >= 7.3.1 (for Linux environments)
2020- mac OS Apple clang >= 11.0.0 (macOS environments)
2121- pthreads
2222- git >= 1.8.3 (required to build and run the HElib test suite)
2323
24+ (* ) On macOS, ideally use cmake 3.17.3+ as it fixes many issues on certain builds on Mojave
25+ onwards.
2426
2527## Option 1: package build (recommended for most users)
2628
@@ -205,7 +207,7 @@ to the `./configure` step.
205207- ` HELIB_DEBUG=ON/OFF ` (default is ` OFF ` ): Activate the debug module when
206208 building HElib (by defining the ` HELIB_DEBUG ` macro). When the debug module
207209 is active, this generates extra information used for debugging purposes.
208- ` HELIB_DEBUG ` will propogate to programs using HElib, when using cmake. When
210+ ` HELIB_DEBUG ` will propagate to programs using HElib, when using cmake. When
209211 this is enabled, programs using HElib will generate a warning during
210212 configuration. This is to remind the user that use of the debug module can
211213 cause issues, such as ` sigsegv ` , if initialized incorrectly.
0 commit comments