3. Create a directory where the binaries will be built. The typical choice is a subfolder "build". In this case, the commands are:
```
git submodule sync --recursive
git submodule update --init --recursive
```
4. Create a directory where the binaries will be built. The typical choice is a subfolder "build". In this case, the commands are:
```
```
mkdir build
mkdir build
cd build
cd build
...
@@ -57,14 +52,14 @@ cmake ..
...
@@ -57,14 +52,14 @@ cmake ..
```
```
Note that cmake will check for any system dependencies that are needed for the build process.
Note that cmake will check for any system dependencies that are needed for the build process.
5. The PALISADE distribution includes some external libraries, such as GMP. NTL and tcmalloc. If you want to use any of these libraries, enable them when you run cmake to force them to build (see instructions on cmake options).
4. The PALISADE distribution includes some external libraries, such as GMP. NTL and tcmalloc. If you want to use any of these libraries, enable them when you run cmake to force them to build (see instructions on cmake options).
6. Build PALISADE by running the following command (this will take few minutes; using the -j<threads> make command-line flag is suggested to speed up the build)
5. Build PALISADE by running the following command (this will take few minutes; using the -j<threads> make command-line flag is suggested to speed up the build)
```
```
make
make
```
```
7. Install PALISADE in a system directory (if desired or for production purposes)
6. Install PALISADE in a system directory (if desired or for production purposes)