| Windows | [](https://ci.appveyor.com/project/skvark/opencv-python) |
The aim of this repository is to provide means to package each new [OpenCV release](https://github.com/Itseez/opencv/releases) for the most used Python versions and platforms.
At the same time it allows anyone to build a custom version of OpenCV for any Python version: just fork this repo and modify the ``appveyor.yml`` (I'll add Travis later for OS X and GNU/Linux) to fit your needs.
At the same time it allows anyone to build a custom version of OpenCV for any Python version: just fork this repo and modify the build files and scripts to fit your needs.
## Why?
...
...
@@ -31,19 +31,18 @@ The project is structured like a normal Python package with a standard ``setup.p
2. Upgrade pip and install numpy for each Python version
3. Build OpenCV
- tests are disabled, otherwise build time increases too much
- build runs twice, once for 32bit and once for 64bit
- both of these builds produce two ``.pyd`` files, one for py2 and one for py3
4. Copy each ``.pyd`` file one by one to cv2 folder of this project and generate wheel
4. Copy each ``.pyd/.so`` file to cv2 folder of this project and generate wheel
5. Install the generated wheels for each Python version
6. Test that the Python versions can import them
7. TO DO: upload the wheels to PyPi
Currently the ``setup.py`` file parses OpenCV version information from the OpenCV sources. OpenCV depends on numpy, so ``setup.py`` checks the numpy version also with the help of pip.
As described earlier, the ``.pyd`` file is normally copied to site-packages. I don't want to pollute the root folder, so the ``__init__.py`` file in cv2 folder handles the import logic correctly by importing the actual ``.pyd`` module and replacing the imported cv2 package in ``sys.modudes`` with the ``.pyd`` module.
As described earlier, for example the ``.pyd`` file on Windows is normally copied to site-packages. I don't want to pollute the root folder, so the ``__init__.py`` file in cv2 folder handles the import logic correctly by importing the actual ``.pyd`` module and replacing the imported cv2 package in ``sys.modudes`` with the cv2 module to retain backward compatibility.
## Many linux wheels
Linux wheels are built using [manylinux](https://github.com/pypa/python-manylinux-demo)
## Manylinux wheels
Linux wheels are built using [manylinux](https://github.com/pypa/python-manylinux-demo). These wheels should work out of the box for most of the distros out there since they are built against an old version of glibc.
## Versioning
...
...
@@ -51,6 +50,18 @@ Currently the ``find_version.py`` script searches for the version information fr
## Supported Python versions
As Python's 2.x releases are slowly approaching legacy state, 2.7.x releases will be the only supported Python 2 versions. On Python 3 side, builds will be run only for the latest release which is at the moment 3.5.1.
#### Windows:
There's a build time limitation (AppVeyor open source builds may take max. 1 hour) which restricts the supported Python versions to two. As Python's 2.x releases are slowly approaching legacy state, 2.7.x releases will be the only supported Python 2 versions on Windows. On Python 3 side, builds will be run only for the latest release.
However, if you wan't to get some other versions, just fork this repo and change the dependencies.
#### Linux
Manylinux wheels are built for all the Python versions which are supported by the manylinux containers.
#### OS X
TODO
There's also a build time limitation (AppVeyor open source builds may take max. 1 hour) which restricts the supported Python versions to two. However, if you wan't to get some other versions, just fork this repo and change the dependencies.
