Default paths / configuration.

[GoogleCodeExporter]

On UNIX (Linux, Mac OS X, FreeBSD, Solaris, etc.) there are a set of common
paths for finding headers, libraries, and binary files. In addition, there
are environment variables such as PATH, LIBRARY_PATH, CPATH, and
LD_LIBRARY_PATH which may be used to augment the default paths. I think it
is a bug that PyOpenCV requires one to create/copy+edit a "config.py" file,
given that most packages are capable of following these standard
conventions and automatically figuring out the correct locations.
Additionally, requiring an explicit configuration causes the standard
installation via setuptools "sudo easy_install -O2 pyopencv" to fail.

Original issue reported on code.google.com by michaelsafyan on 5 May 2010 at 1:20

[GoogleCodeExporter]

Thanks, Michael. I'll see what I can do to avoid using config.py.

Cheers,
Minh-Tri

Original comment by pmtri80@gmail.com on 6 May 2010 at 9:00

• Changed state: Accepted

[GoogleCodeExporter]

Starting from r1025, PyOpenCV can be build via CMake (thanks Dat) as well as 
via setuptools. bjam is no longer required. File 'config.py' is still needed 
but it is automatically created via CMake. If you have time, please feel free 
to try it out on your platform and let me know if there is any problem. 

To install PyOpenCV via CMake:
mkdir build
cd build
cmake ..
make
make install

To install PyOpenCV via setuptools (PyOpenCV will automatically invoke CMake to 
self-configure if the file 'config.py' is not found):
python setup.py install 

For now, I'd like to close this issue. Please don't hesitate to open a new 
issue if the problem persists. Thank you very much for your feedback.

Best regards,
Minh-Tri

Original comment by pmtri80@gmail.com on 27 Aug 2010 at 7:55

• Changed state: Fixed