Raffaele Signoriello

I did the uninstall and I ran again the PyVSC installer. Before doing it I fired the pip install PyBoolector command and it seems like is running across many versions...

I installed Boolector by building it from the git repo without any problem at moment. The main obstacle I'm struggling with is how to avoid installing PyBoolector from PYCSV installation...

adding the ticket as reference https://github.com/Boolector/boolector/issues/180

Hello all, made quite few progresses today: 1. Ran the following instruction in the boolector repo ./configure.sh --python && cd build && make 2. linked the /build/lib in the PYTHONPATH...

OK found the issue why is not working on py3: the following is the Python2 configuration while running the configure: This is instead the py3:  I can clearly see...

Sorry yes it is exactly what I was about to add, this is the result got by using both --python and --py3: Yes to answer your question I removed the...

I was hacking around the Cmakelist.txt with no result at moment, I will go for your suggestions as well. Thanks again

I added this line after running the ```python3.9-config --includes ``` this hardcoded line fixes the issues now the BIND is done properly and I'm able to run the following command...

I think I can close, I will experiment all the features of PYVSC and see if missing something in the installation (hope not)

Last question before closing, is the pyboolector the only dep? since i ran the pip install with no deps I'm wondering if could have missed something else