Commit a9af17d1 authored by Yuriy Polyakov's avatar Yuriy Polyakov

v1.7.b documentation updates

parent 0ab3bd95
Pipeline #105636532 failed with stages
in 295 minutes and 2 seconds
......@@ -103,7 +103,7 @@ endif()
......@@ -82,7 +82,7 @@ After the "make" completes, you should see the PALISADE library files in the lib
make install
You would probably need to run "sudo make install" unless you are specifying some other install location. You can change the install location by running
"cmake -DCMAKE_INSTALL_PREFIX=/your/path ..".
"cmake -DCMAKE_INSTALL_PREFIX=/your/path ..". The header files are placed in the "include/palisade" folder of the specified path, and the binaries of the library are copied directly to the "lib" folder. For example, if no installation path is provided in Ubuntu (and many other Unix-based OSes), the header and library binary files will be placed in "/usr/local/inlude/palisade" and "/usr/local/lib", respectively.
Testing and cleaning the build
12/26/2019: PALISADE v1.7.c is released
* Fixes a bug affecting applications using the PALISADE serialization capability
* Changes the installation paths for header files and library binary files
12/19/2019: PALISADE v1.7.b is released
* Simplifies the development of applications using PALISADE (only one header file is now needed for most applications)
No preview for this file type
......@@ -38,7 +38,7 @@ PROJECT_NAME = "PALISADE Lattice Crypto Library"
# could be handy for archiving the generated documentation or if some version
# control system is used.
# Using the PROJECT_BRIEF tag one can provide an optional one line description
# for a project that appears at the top of each page and should give viewer a
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment