Closed sigveka closed 9 years ago
Hi Sigve,
please try putting something like
if(APPLE) set(CMAKE_SHARED_LIBRARY_SUFFIX ".so") endif(APPLE)
into
src/src/CMakeLists.txt
and check whether the examples still work.
Henrik
Fantastic, that seems to be a permanent solution to the problem.
A comment from stackoverflow regarding importing dylib Python modules on OS-X:
"Just use *.so as your module extensions in OS X too. I have a vague memory of not being able to load .dylib's and it turning out to be an issue with python itself. . . but I can't find the mailing list post now.
However, rest assured you're following standard practice by using .so's even on OS X. The only .dylib's in the entire framework are the libsvn_swig ones.-"
I was having problems importing the Python module "modena" as the error message shows:
The root of the problem turned out to be that Python has a problem with shared objects with
dylib
extension, for some reason Python can not findlibmodena.dylib
in$HOME/lib
. The error was "fixed" by adding the symboliclibmodena.so
link pointing tolibmodena.dylib
.Open a Terminal window and change to the directory containing the dynamic libraries:
(not necessary just for information) The problem is that Python does not seem to find the shared objects (which on a Mac has the extension
dylib
). While it is possible to change the extension to.so
, this did not solve the problem for me.The solution was to create a symbolic link as follows:
As shown below this solved the problem, however it remains unclear why Python does not support
dylib
extensions.