From: Bob on 11 Jan 2010 11:24 We have successfully created several DLLs written in Matlab, compiled with the MATLAB Compiler, and run on machines using version 7.8 of the runtime (i.e. MCR7.8, part of R2008a) installed. Now, however, the engineer who wrote the originals has moved on, but we asked him to write a new DLL, which he has done. In his new location, he has R2008b at his disposal, so he used that to deliver the new DLL. Of course, that doesn't work on our machines, as they don't have version 7.9 of the runtime (MCR7.9). So, I tried to install MCR7.9, and we continue to get failures, specifically an access violation within libmx.dll, an attempt to read from address 0x24. I also tried recompiling the DLL using our version, and get the same failure with MCR7.8. These efforts were all using Windows XP. Finally, I tried installing MCR7.8 and MCR7.9 on a Windows Vista machine that has never had any MathWorks software installed, and both versions of the DLL work just fine! So, it seems that multiple versions of the MCR are okay, but not if the development environment is present?! I also tried removing everything MATLAB related on one of the failing machines (using both uninstallers and RegEdit), then just installing MCR7.8, but I still get the problem. I also tried setting the PATH as suggested in the documentation. Any ideas on how this can be resolved? I'm at my wits end! Thanks, -Bob
From: Image Analyst on 11 Jan 2010 12:02 Bob: I don't know, but I have the runtime library (MCR) and the full MATLAB development environment on my computer and they seem to be happy with each other - I can run executables. However I haven't tried running an executable that runs a DLL compiled with MATLAB. The Mathworks tech support can help you - they helped me with a tricky compiler problem last week.
|
Pages: 1 Prev: 64bits and memory problem Next: making a movie in matlab out of matrix of intensity values |