You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 7, 2022. It is now read-only.
Hello PyTango community,
recently I've been trying to compile PyTango on CentOS 7.7 with boost version 1.69 using Python 3.6. In CentOS, it is accessible under boost169, not boost in /usr/lib64 or /usr/include. I had to make symbolic link in order to make it work.
Apart from that, there was wrong assumption of boost python library name. It looks for libboost_python3, but there's libboost_python36.
AFAIK, all logic responsible for discovering platform, libraries and similar stuff is present in setup.py, right? In case of any change or adaptation, it requires manual maintainer intervention.
AFAIK compilation on Windows utilises CMake to handle all those paths and cases. What about using CMake to compile PyTango on both Linux and Windows? I haven't tested it but maybe CMake could take care of proper libraries discovery.
The text was updated successfully, but these errors were encountered:
Hi @stanislaw55.
Sorry for delay on this one. OK, so you have manually installed a newer version of Boost (Centos 7 comes with 1.53). That's a bit harder to handle than just the standard version for each major OS.
Yes, the logic for discovering the platform, libraries, etc. is in setup.py. Using CMake could help, and yes we are using it for the Windows compilation, but the boost version is almost hard coded in there. If you can propose something with CMake that solves the problem on Linux, great! I don't know much about it.
@stanislaw55 Would you mind testing the branch from the linked PR, please?
Also note that if you have a custom boost installation, the BOOST_ROOT and newly added BOOST_LIB environment variables may need to be set when running python setup.py build.
Hello PyTango community,
recently I've been trying to compile PyTango on CentOS 7.7 with boost version 1.69 using Python 3.6. In CentOS, it is accessible under
boost169
, notboost
in/usr/lib64
or/usr/include
. I had to make symbolic link in order to make it work.Apart from that, there was wrong assumption of boost python library name. It looks for
libboost_python3
, but there'slibboost_python36
.AFAIK, all logic responsible for discovering platform, libraries and similar stuff is present in
setup.py
, right? In case of any change or adaptation, it requires manual maintainer intervention.AFAIK compilation on Windows utilises CMake to handle all those paths and cases. What about using CMake to compile PyTango on both Linux and Windows? I haven't tested it but maybe CMake could take care of proper libraries discovery.
The text was updated successfully, but these errors were encountered: