From @demisjohn on February 28, 2018 8:17
Current implementation requires the user to build/install many MacPorts packages. For example, boost-python-mt.dylib must be found at /opt/local/lib/libboost_python-mt.dylibin order for python to load_camfr.so` properly.
Would prefer to statically link these libraries, so that _camfr.so contains the required libs, allowing for a MacOS "installer" to simply put the camfr/ module folder into the system site-packages and it works, without the user needing to install anything on macports. Also, link against any MacOS dynamic system libraries, or else build them into the module statically.
How do you write setup.py to do that?
From @demisjohn on February 28, 2018 8:17
Current implementation requires the user to build/install many MacPorts packages. For example,
boost-python-mt.dylibmust be found at /opt/local/lib/libboost_python-mt.dylibin order for python to load_camfr.so` properly.Would prefer to statically link these libraries, so that
_camfr.socontains the required libs, allowing for a MacOS "installer" to simply put thecamfr/module folder into the systemsite-packagesand it works, without the user needing to install anything on macports. Also, link against any MacOS dynamic system libraries, or else build them into the module statically.How do you write
setup.pyto do that?