Open djorlando24 opened 4 years ago
For the record, without editing the configure script the following output is produced.
checking for boostlib >= 1.20.0... yes
checking whether the Boost::Python library is available... yes
checking whether boost_python is the correct library... no
checking whether boost_python is the correct library... (cached) no
checking whether boost_python3 is the correct library... no
checking for boostlib >= 1.20.0... yes
checking whether the Boost::Python library is available... (cached) yes
checking whether boost_python is the correct library... (cached) no
checking whether boost_python is the correct library... (cached) no
checking whether boost_python3 is the correct library... (cached) no
Linking will then fail when running make
with the above configure output.
With the edits, the following output is produced, and linking succeeds.
checking whether the Boost::Python library is available... yes
checking whether boost_python38 is the correct library... yes
checking for boostlib >= 1.20.0... yes
checking whether the Boost::Python library is available... (cached) yes
checking whether boost_python38 is the correct library... (cached) yes
I have to modify lines 17046 and 17458 of
configure
to get MacOS to find my libboost_python, since homebrew's current version calls the librarylibboost_pythonXX.dylib
where XX is 27 or 38 etc, depending on the version of Python used.configure
is just hunting forlibboost_python.so
which is symlinked on Linux but not on MacOS homebrew. Making such a symlink is dangerous if you have multiple python versions. Suggest modifyingconfigure
to use python version to go looking for libboost_python in the right place on Darwin.