comp.soft-sys.matlab - The MathWorks calculation and visualization package.
Hello I am running a matlab compiler .exe sent by a client. When I run a batch file which calls the .exe i get the msg "Toolbox Path Cache is not being used. Type 'help toolbox_path_cache' for more info" Is this a problem? What can we do about it? We are seeing some very weird problems happening in our GAMS code (the matlab .exe invokes a GAMS session and runs our model) wrt accessing data from an excel spreadsheet so we need to trace if this is happening because of the listed issue above when Matlab is running. We have matlab R14 installed (not compiler) on this machine, but we do not have the .m file used to create this .exe (and may not be able to get it) so cannot run the matlab code manually. Regards A
I am trying to run a standalone executable file on a deployment machine that does not have matlab installed on it. When I run the MCRInstaller.exe it works normally at the beginning and after two or three steps(right before starting the installation) it tells me "MCRInstaller was interrupted. Your system was not modified....." What is the problem? If anyone had this problem before plz tell me Thanks
Fix for MCR Not Available message with Combuilder in Windows boxes. We couldn't get DLLs built with Combuilder in R14 to work. They'd register but give us an error saying "MCR Not Available" when we accessed them. After a lot of trial and error we found that if we register our DLLs in the directory FROM which the MCR was installed, they work. The weird thing is that it's not the directory we installed TO, it's the directory we installed FROM. We copied the MCR installer to a directory named C:\INSTALLS. We ran the MCRInstaller.MSI program and chose to install in "C:\Program Files\MathWorks\MATLAB Component Runtime". Now we register our files in C:\Installs and they work. Plus we discovered that we don't need the CTF files that the doc says we need. They don't hurt, but they don't help at all. Having the install directory or the application executable directory in the path doesn't help either. The only reference to C:\INSTALLS that I can find in our registry are under the MCR's key in: HKEY_LOCAL_MACHINE\SOFTWARE\Clsses\Installer\Products\45179633990D5442AF2089455D9B422\SorceList and HKEY_LOCAL_MACHINE\SOFTWARE\Clsses\Installer\Products\45179633990D5442AF2089455D9B422\SorceList\Net I assume the key number after \Products\ would be different for each installation but you can search on Matlab to find your key. Later we'll experiment with changing these registry values but for now I wanted to share what we learned.
So far a I've noticed a few things while tring to build an application using compiled matlab libraies. If anyone understands why I'd appreciate it!!! First background: My windows app is in VC++ 7.1, I'm using matlab 7.0 R14. I have 2 compile libraries, call them lib1 and lib2. I always call mclInitializeApplication() once at App level when the app starts and call mclTerminateApplication() once at the App end level. That's where the similarities end. 1. On the development machine, I can initialize and terminate lib1 and lib2 to mye heart's content, I can do it every time i call a library routine. If I build and run this on a deployment machine with MWCR installed, it will not initialize any library after any other library has bee terminated. In other words lib1Initialize() lib1Terminate() lib2Initialize() --> will fail here lib2Terminate() will not work. lib1Initialize() lib2Initialize() lib1Terminate() lib2Terminate() does work but you cannot initialize any library after the first libTerminate is called. 2. If I decide to move the lib1 and lib2 initialize to the app level and only do it once (and move lib1 and lib2 terminate to the App destructor) it now works on the deployment machine but not on my development machine with the full matlab installed. On my development machine, it crashes at the first libInitialize, doesn't matter which one I put first. Weird, hunh? All I want is a single version of software that works on both machines. Understanding what's going on would be nice as well.