Compilation of matlab bindings should use the matlab_add_mex CMake function

[traversaro]

We had problems related to that in getting the bindings to work in Windows.

[traversaro]

We would avoid to manually do this like this: ab0ecc4 .

[traversaro]

This could also avoid symbols clash between system libraries and matlab libraries (as this one: robotology-legacy/codyco-superbuild#141), see this comment in FindMatlab.cmake ,

idyntree/cmake/FindMatlab.cmake

Line 907 in 39bcd48

# if we do not do that, the symbols linked from eg. boost remain weak and

:

   # if we do not do that, the symbols linked from eg. boost remain weak and
   # then clash with the ones defined in the matlab process. So by default
   # the symbols are hidden.
   # This also means that for shared libraries (like MEX), the entry point
   # should be explicitly declared with default visibility, otherwise Matlab
   # cannot find the entry point.
   # Note that this is particularly meaningful if the MEX wrapper itself 
   # contains symbols that are clashing with Matlab (that are compiled in the
   # MEX file). In order to propagate the visibility options to the libraries 
   # to which the MEX file is linked against, the -Wl,--exclude-libs,ALL
  # option should also be specified.