added Cyrillic;

added Cyrillic;

replace binary format with hex;

move duplicated code to inline function;
fixing issue with "ёЁ";
Fixing bug in NAryMatIterator documentation(Bug #3787).

Fixed the non-working code example for NAryMatIterator.
The documentation of NAryMatIterator in file:
modules/core/include/opencv2/core/core.hpp has a working example which
was used for these edits.
TCP instead of UDP
Merge pull request #3307 from ilya-lavrenov:ffmpeg_rtsp
fix issue with font;
Patch for NDK r10
silence cmake 3.0+ warnings on LOCATION attribute
Merge pull request #3327 from JonasVautherin:patch_cmake_android_r10
Merge pull request #3300 from rohitrawat:bug_3787_docs_NAryMatIterator
Merge pull request #3329 from taka-no-me:patch-1
Merge pull request #3265 from BKNio:putText_develop
core: fix x86 PIC code compilation

This bug was triggered by Buildroot autobuilders [1,2], causing this
kind of failures [3,4]:

  [ 14%] Building CXX object modules/core/CMakeFiles/opencv_core.dir/src/system.cpp.o
  /home/test/autobuild/instance-0/output/build/opencv-2.4.10/modules/core/src/system.cpp: In function '(static initializers for /home/test/autobuild/instance-0/output/build/opencv-2.4.10/modules/core/src/system.cpp)':
  /home/test/autobuild/instance-0/output/build/opencv-2.4.10/modules/core/src/system.cpp:280:10: error: inconsistent operand constraints in an 'asm'
  make[3]: *** [modules/core/CMakeFiles/opencv_core.dir/src/system.cpp.o] Error 1

[1] http://buildroot.org/
[2] http://autobuild.buildroot.org/
[3] http://autobuild.buildroot.org/?reason=opencv-2.4.10
[4] http://autobuild.buildroot.org/results/483/4838285b25d6293a5cf0bb9eadd5040a7c75d766/build-end.log

Signed-off-by: Samuel Martin <s.martin49@gmail.com>
Merge pull request #3331 from tSed:opencv-2.4.x/fix-x86-PIC-compilation
ocl: Change static variable order in cl_context.cpp to avoid crashes during destruction

ContextImpl::currentContext contains a reference to one of the
DeviceInfoImpl objects from:

static std::vector<DeviceInfoImpl> global_devices;

ContextImpl::currentContext is destroyed in the destructor
for the statically defined object __module, and relies on its
DeviceInfoImpl reference to query some hardware features while
being destroyed.

This means that we need to ensure that the global_devices vector is
destroyed affter __module, otherwise ContextImpl::currentContext's
DeviceInfoImpl reference will no longer be valid when __module is
destroyed.

Since these variables are all confined to a single compilation unit,
they will be destruct from bottom to top, so we need to make sure
that __module is the bottom definition so it can be destroyed first.
Merge pull request #3337 from tstellarAMD:2.4-ocl-context-cleanup-fix
iOS: fix crash from overrelease in UIImageToMat
fix installation layout for debian packages:

Install symlinks to shared libraries as a part of development package,
not runtime package.

It is default behavior for debian packages.
Merge pull request #3340 from AdLantis:2.4
viz: fixed memory leak, issue 3961