2016-09-01 01:30:58 -0600 | commented question | Build Python bindings separately Ahh, okay. That makes sense, thanks for the link. |
2016-08-31 23:57:10 -0600 | commented question | Build Python bindings separately But do some of the bits of the Python bindings live in the main OpenCV libraries, not just cv2? Otherwise, why does building the Python bindings need to re-build OpenCV modules? |
2016-08-31 23:47:08 -0600 | commented question | Build Python bindings separately Hmm, okay - so some of the OpenCV modules depend on libpython.so? That seems unfortunate. |
2016-08-31 23:30:28 -0600 | commented question | Build Python bindings separately That would still involve rebuilding OpenCV for each version of Python, yes? I wanted to just build the Python bindings (i.e. |
2016-08-31 22:41:17 -0600 | asked a question | Build Python bindings separately Hi, Is it possible to build the Python bindings for OpenCV separately to the main build - something like a standard distutils setup.py? On our supercomputer cluster we maintain quite a few versions of Python. As with all packages, each new version gets built and installed into it's own directory. Each of these versions needs their own Python bindings, linked against that particular version of Python, so what we usually do is install the main C/C++ libraries as usual and then build Python packages for each version as needed, linking against the already-installed C/C++ libraries. However, I can't work out how to separate the Python binding build for OpenCV from the main C/C++ build. Our base application tree looks like this at the moment:
and we want to build and install the bindings at
The we can easily allow users to mix and match Python and OpenCV versions using the standard environment modules (e.g. doing Could you let me know how we can do this? Thanks, Ben |