Compiling with Image Acquisition Toolkit
in [Matlab]
|
From: Tim on 9 Mar 2010 00:30 I can compile m files (using mcc explicitly, or deploytool) and run them on a remote machine with the MCR. When I try an m file that uses the Image Acquisition Toolkit, things go wrong. I get an error like this one: ??? Error using ==> videoinput.videoinput at 90 Invalid MEX-file 'C:\DOCUME~1\avu\LOCALS~1\Temp\avu\mcrCache7.9\Select0\toolbox\imaq\imaq\imaqmex.mexw32': The specified module could not be found. .. MATLAB:invalidMEXFile Can anyone help? Thanks in advance, Tim
From: Husam Aldahiyat on 9 Mar 2010 01:32 "Tim " <tim.bate(a)gmail.com> wrote in message <hn4mde$gmu$1(a)fred.mathworks.com>... > I can compile m files (using mcc explicitly, or deploytool) and run them on a remote machine with the MCR. > > When I try an m file that uses the Image Acquisition Toolkit, things go wrong. I get an error like this one: > > ??? Error using ==> videoinput.videoinput at 90 > Invalid MEX-file 'C:\DOCUME~1\avu\LOCALS~1\Temp\avu\mcrCache7.9\Select0\toolbox\imaq\imaq\imaqmex.mexw32': The specified module could not be found. > > . > > MATLAB:invalidMEXFile > > Can anyone help? Thanks in advance, > Tim You cannot deploy certain functions in certain toolboxes. There is a list of supported toolboxes for compilation but Im not bothered to fetch it. Image Aquisition is probably one of the toolboxes that cannot be compiled.
From: Tim on 9 Mar 2010 02:06 A good idea, Husam, and one of the things I thought of. That's not it, or shouldn't be, as I've checked the list. I should have mentioned that, sorry. For my version (R2008b) the only tool it doesn't compile (supposedly) is imaqtool, which I don't use. Since my last post, I tried imaqfind, and it works fine, so some of the toolkit is working. imaqhwinfo causes the same error. imaqfind, of course, returns nothing; I can't create a video object to HAVE in memory. "Husam Aldahiyat" <numandina(a)gmail.com> wrote in message <hn4q15$aej$1(a)fred.mathworks.com>... > "Tim " <tim.bate(a)gmail.com> wrote in message <hn4mde$gmu$1(a)fred.mathworks.com>... > > I can compile m files (using mcc explicitly, or deploytool) and run them on a remote machine with the MCR. > > > > When I try an m file that uses the Image Acquisition Toolkit, things go wrong. I get an error like this one: > > > > ??? Error using ==> videoinput.videoinput at 90 > > Invalid MEX-file 'C:\DOCUME~1\avu\LOCALS~1\Temp\avu\mcrCache7.9\Select0\toolbox\imaq\imaq\imaqmex.mexw32': The specified module could not be found. > > > > . > > > > MATLAB:invalidMEXFile > > > > Can anyone help? Thanks in advance, > > Tim > > You cannot deploy certain functions in certain toolboxes. > There is a list of supported toolboxes for compilation but > Im not bothered to fetch it. Image Aquisition is probably > one of the toolboxes that cannot be compiled.
From: Tim on 9 Mar 2010 03:02 I have created a VERY simple m file, which is as follows: a = imaqhwinfo display a Even this doesn't work (works fine on my matlab machine, but no other after compiling.) Error is still a mex-file error. Included below: ??? Error using ==> imaqhwinfo at 61 Invalid MEX-file 'C:\DOCUME~1\avu\LOCALS~1\Temp\avu\mcrCache7.9\test6_1\toolbox\imaq\imaq\imaqmex.mexw32': The specified module could not be found. .. MATLAB:invalidMEXFile Really could use help :) Imaq is a very expensive toy if I can't deploy it! Thanks, Tim "Tim " <tim.bate(a)gmail.com> wrote in message <hn4s0s$ec3$1(a)fred.mathworks.com>... > A good idea, Husam, and one of the things I thought of. That's not it, or shouldn't be, as I've checked the list. I should have mentioned that, sorry. For my version (R2008b) the only tool it doesn't compile (supposedly) is imaqtool, which I don't use. > > Since my last post, I tried imaqfind, and it works fine, so some of the toolkit is working. imaqhwinfo causes the same error. imaqfind, of course, returns nothing; I can't create a video object to HAVE in memory. > > > "Husam Aldahiyat" <numandina(a)gmail.com> wrote in message <hn4q15$aej$1(a)fred.mathworks.com>... > > "Tim " <tim.bate(a)gmail.com> wrote in message <hn4mde$gmu$1(a)fred.mathworks.com>... > > > I can compile m files (using mcc explicitly, or deploytool) and run them on a remote machine with the MCR. > > > > > > When I try an m file that uses the Image Acquisition Toolkit, things go wrong. I get an error like this one: > > > > > > ??? Error using ==> videoinput.videoinput at 90 > > > Invalid MEX-file 'C:\DOCUME~1\avu\LOCALS~1\Temp\avu\mcrCache7.9\Select0\toolbox\imaq\imaq\imaqmex.mexw32': The specified module could not be found. > > > > > > . > > > > > > MATLAB:invalidMEXFile > > > > > > Can anyone help? Thanks in advance, > > > Tim > > > > You cannot deploy certain functions in certain toolboxes. > > There is a list of supported toolboxes for compilation but > > Im not bothered to fetch it. Image Aquisition is probably > > one of the toolboxes that cannot be compiled.
From: Ashish Uthama on 9 Mar 2010 09:25
On Tue, 09 Mar 2010 03:02:04 -0500, Tim <tim.bate(a)gmail.com> wrote: > I have created a VERY simple m file, which is as follows: > > a = imaqhwinfo > display a > > Even this doesn't work (works fine on my matlab machine, but no other > after compiling.) Error is still a mex-file error. Included below: > > ??? Error using ==> imaqhwinfo at 61 > Invalid MEX-file > 'C:\DOCUME~1\avu\LOCALS~1\Temp\avu\mcrCache7.9\test6_1\toolbox\imaq\imaq\imaqmex.mexw32': > The specified module could not be found. > > . > > MATLAB:invalidMEXFile > > Really could use help :) Imaq is a very expensive toy if I can't deploy > it! > > Thanks, > Tim Tim, you could contact tech support for immediate help: http://www.mathworks.com/support/contact_us/index.html The invalid mex file error is usually thrown when a dependency (dll file) for that mex file is missing/not on path. I would guess that a required driver is missing on the deployment machine. Did you have to install any third party libraries/dlls/drivers on your source machine to enable this functionality? Does the compiled app work fine on the same machine that it was compiled on? If so, its a good indication of the above. |