A fork of https://github.com/openfheorg/openfhe-python to add some missing functionality
|
3 months ago | |
---|---|---|
.github | 5 months ago | |
docker | 6 months ago | |
docs | 6 months ago | |
examples | 5 months ago | |
openfhe | 6 months ago | |
src | 3 months ago | |
.gitignore | 6 months ago | |
CMakeLists.txt | 5 months ago | |
LICENSE | 1 year ago | |
README.md | 5 months ago | |
build_package.sh | 6 months ago | |
setup.py | 6 months ago |
Please see Instructions for the Docker setup
Before building, make sure you have the following dependencies installed:
We recommend following OpenFHE C++ installation instructions first (which covers Linux, Windows and MacOS) and then getting back to this repo. See notes on installing pybind11
below
To install OpenFHE-python directly to your system, ensure the dependencies are set up. Then clone the repository, open a terminal in the repo folder and run the following commands:
pip install "pybind11[global]"
mkdir build
cd build
cmake .. # Alternatively, cmake .. -DOpenFHE_DIR=/path/to/installed/openfhe if you installed OpenFHE elsewhere
make
make install # You may have to run sudo make install
At this point the .so
file has been built. Your exact installation process will depend on your virtual environment.
Cmake will automatically find the python installation path, if unwanted, you can specify the python path by adding -DPYTHON_EXECUTABLE_PATH=/path/to/python
to the cmake command.
If you see an error saying that one of OpenFHE .so files cannot be found when running a Python example (occurs only for some environments),
add the path where the .so files reside to the PYTHONPATH
environment variable:
export PYTHONPATH=(path_to_OpenFHE_so_files):$PYTHONPATH
In some environments (this happens rarely), it may also be necessary to add the OpenFHE libraries path to LD_LIBRARY_PATH
.
Alternatively you can install the library and handle the linking via Conda. Clone the repository, open a terminal in the repo folder and run the following commands:
conda create -n ${ENV_NAME} python=3.{X} anaconda
where ${ENV_NAME}
should be replaced with the name of your environment, and {X}
should be replaced with your desired python version. For example you might have
conda create -n openfhe_python python=3.9 anaconda
. Now, you would install pybind11
either via:
pip install "pybind11[global]"
or via conda install -c conda-forge pybind11
, but for now we recommend using the first method, with pip. Some users have reported issues when using the conda pybind11
Now, you would clone the repository, and run the following commands to install :
mkdir build
cd build
cmake .. # Add in -DOpenFHE_DIR=/path/to/installed/openfhe if you installed OpenFHE elsewhere
make
make install # You may have to run sudo make install
Then, you can develop the library to link
cd ..
mkdir lib
mv *.so lib
conda develop lib
which creates a lib folder, moves the built .so
file into that lib folder, and tells conda where to look for external libraries.
Note You may wish to copy the .so
file to any projects of your own, or add it to your system path to source from.
To get familiar with the OpenFHE Python API, check out the examples:
OpenFHE Python Wrapper API Reference