On 2019-8-1 08:45 , Ruben Di Battista wrote: > :info:configure -- Looking for feenableexcept - not found > :info:configure -- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY > :info:configure -- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success > :info:configure -- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY > :info:configure -- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY > - Success > :info:configure -- Performing Test COMPILER_HAS_DEPRECATED_ATTR > :info:configure -- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Success > :info:configure -- Found PythonLibs: /opt/local/lib/libpython3.7.dylib > > ``` > > So it finds Python 3.7, but the library path is wrong. How is this > possible? Anyone can give me an hint?
No idea, you'd have to look at what its CmakeLists is doing. It's clearly not using any of the recommended ways to find out how to link against python though: % python3.7-config --ldflags -L/opt/local/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/config-3.7m-darwin -lpython3.7m -ldl -framework CoreFoundation % pkg-config --libs python-3.7 -L/opt/local/Library/Frameworks/Python.framework/Versions/3.7/lib -lpython3.7m Hopefully there is a cmake variable that can be set to influence where it looks. - Josh
