http://bugs.winehq.org/show_bug.cgi?id=5040
------- Additional Comments From al.danial@ngc.com 2006-10-04 13:42 ------- As Dan mentioned we usually run matlab on Linux--and prefer that over Windows because we can then blast the code through our Linux clusters. In this particular case we have m files plus C code that has to be compiled into mex files. A DLL (for which we do not have source code) accompanies the C code so we have to compile and link in Windows and generate a Windows mex file which is only callable from matlab running under Windows.
Actually this is only half the story; it gets more complicated. Once matlab (for Windows) is installed we want to use the matlab compiler, mcc, to build a stand-alone executable and will want to run that executable under Wine. Stand- alone matlab executables do not use matlab licenses when they run. This gives us the freedom to run the executable on many more cluster nodes than we have matlab licenses.
As a proof of concept, I compiled a trivial m file on a Windows machine to create a Windows .exe then transfered that to my Linux box to run that under Wine. That fails too but I won't file a bug for that yet (too many other possible reasons for failure, most to do with inability to locate runtime libraries). I'm hoping that if I have a working matlab-for-Windows in Linux, executables generated by the mcc compiler will also run under Wine.
Yes, I'm probably nuts for expecting all of this to work but Wine has impressed me sufficiently in the past that I actually think this can be pulled off.