MATLAB R2015b supports Mac OS X 10.11 (El Capitan).
For more information on which versions of MATLAB are supported on Mac, please refer to the platform roadmap for Mac:
Workarounds for issues that may arise when running MATLAB in El Capitan are listed below:
1) Xcode 7 Support in MEX
Users will encounter an error when attempting to setup MEX with the compilers packaged in Xcode 7. Out of the box, MATLAB R2015b will not detect Xcode 7’s “clang” compiler. Users will receive the following error:
>> mex -setup
Error using mex
No supported compiler or SDK was found. For options, visit
http://www.mathworks.com/support/compilers/R2015a/maci64.html.
Please refer to the following link for adding XCode 7 support to R2015b:https://www.mathworks.com/matlabcentral/answers/246507-why-can-t-mex-find-a-supported-compiler-in-matlab-r2015b-after-i-upgraded-to-xcode-7-0
2) Java Exception Upon Startup in MATLAB R2014a and Earlier
Upon startup, releases of MATLAB R2014a and earlier may trigger a Java exception and terminate abruptly. They display the following error message:
java.lang.NullPointerException
at
com.mathworks.widgets.WindowsWidgetFactory$SearchAndClearButton.anyText(WindowsWidgetFactory.java:187)
at
com.mathworks.widgets.WindowsWidgetFactory$SearchAndClearButton.getIcon(WindowsWidgetFactory.java:195)
A patch has been released to resolve the Java crash and can be downloaded from the following bug report:https://www.mathworks.com/support/bugreports/1098655
3) Java 6 in Versions of MATLAB R2013a and Earlier
Versions of MATLAB which require Java 6 (R2013a and earlier), will not launch in El Capitan. El Capitan is not shipped with Java 6 . You can install Java 6 from the following link to enable the versions of MATLAB that use it:https://support.apple.com/kb/DL1572?locale=en_US
4) Full-screen Dialog Boxes
When MATLAB is expanded into Mac OS X's full-screen or split-screen mode, certain dialog boxes will display in full-screen mode. The dialog windows will be stretched beyond their expected dimensions. Unfortunately, there is no workaround for resolving this issue.
