Who knows, maybe the user's Sphinx installation uses a Python we couldn't find.

Most importantly, added support for multiple include directores,
but also did some general cleanup.

Rationale: we already depend on it (e.g. some scripts use print_function).

None of this should be relevant as of CMake 2.8.7.

Rationale: 1.2.3 was a security update, and we should avoid using
versions with known security vulnerabilities.

They're not listed in the documentation for the FindZLIB module,
so we shouldn't use them unless necessary.

* There's no OPENCV_BINARY_DIR variable;
* No need to append CMakeFiles/CMakeTmp, as CMake does it for you;
* Output variables are unused;
* Wrong usage of CMAKE_FLAGS;
* Small quoting and style issues.

(cherry picked from commit aa96d8d0)

It's part of CMake nowadays, too.

In fact, I don't think we actually use it... but I kept the include,
just in case.

This version uses CMake to generate Info.plist, which should be more
reliable than the old approach.

disabled 64f IPP DFT; added IPP Gaussian filter; added IPP GetRectSubPix; added IPP BilateralFilter (temporarily disabled)

Solve the problem seen when using recent versions of CMake (such as 2.8.11): OpenCVConfig.cmake violates the policy CMP0004.

Symptoms:
CMake Error at CMakeLists.txt:10 (add_executable):
Target "my_app" links to item "C:/Program Files " which has leading
or trailing whitespace. This is now an error according to policy CMP0004.

This problem occurs when building on Windows when we depend on libraries located (for example) in "C:\Program Files (x86)..."

On my MacOS the output of the sphinx-build binary is the following:

Error: Insufficient arguments.

Sphinx v1.2b1
Usage: /usr/local/bin/sphinx-build [options] sourcedir outdir [filenames...]

...

I have installed sphinx, but without this change HAVE_SPHINX==0 for me, so I can't build docs.

WITH_WINRT -> ENABLE_WINRT_MODE;
Some temporary char* replaced with Ptr<char>;
Build fix for regular WIN32;
Windows Platform SDK and MSVC search added to cmake;
Warinig fixes.