Prev: ode with boundaries
Next: trisurf matlab
From: Andreu Mora on 4 May 2010 06:59 Hi all, I had to create a MEX file from C code, using external libraries, and also installing Microsoft VC++ compiler. I have succeeded compiling the MEX file, after linking all the libraries, solving problems with DLLs and this stuff. The MEX file is hence created. When I call the MEX file, Matlab claims it is not a valid file, that cannot find the specified module. I have surfed the web for this problem, and seems that DLLs are not correctly set. I have used "DependencyWalker" to see which one is missing, and all of them are right except a warn from MSJAVA.DLL (which DependencyWalker says it's normal). So, I seem to have all the DLL dependencies right, the MEX command compiles, but when I try to execute it fails. Does anyone know something about it? Thanks a lot, Andreu
From: Jan Simon on 4 May 2010 11:43 Dear Andreu! > I had to create a MEX file from C code, using external libraries, and also installing Microsoft VC++ compiler. > > I have succeeded compiling the MEX file, after linking all the libraries, solving problems with DLLs and this stuff. The MEX file is hence created. Did you try to compile on of the examples shipped with Matlab? Jan
From: Andreu Mora on 4 May 2010 12:14 Dear Jan, Thanks for asnwering, I seem not to have any problem compiling the example mex files with MS VC++ compiler, but those are really simple compilations. Do you have any other idea? Thanks, Andreui "Jan Simon" <matlab.THIS_YEAR(a)nMINUSsimon.de> wrote in message <hrpfa8$rf9$1(a)fred.mathworks.com>... > Dear Andreu! > > > I had to create a MEX file from C code, using external libraries, and also installing Microsoft VC++ compiler. > > > > I have succeeded compiling the MEX file, after linking all the libraries, solving problems with DLLs and this stuff. The MEX file is hence created. > > Did you try to compile on of the examples shipped with Matlab? > > Jan
From: Jan Simon on 4 May 2010 12:32 Dear Andreu! > Thanks for asnwering, I seem not to have any problem compiling the example mex files with MS VC++ compiler, but those are really simple compilations. > > Do you have any other idea? Then it might depend on the "external libraries". Are these libs visible when the DLL is called? Jan
From: ImageAnalyst on 4 May 2010 12:43
Jan: The "walker" part of Dependency Walker means that it traces down all the dependencies, so yes, if something were missing, it would notice that and flag it as red color, and if it does find it, it's listed in a normal black color. |