Prev: Doblu-click on a cell in uitable?
Next: varargout{1:nargout}
From: Arne on 18 Jan 2010 14:45
This post is about a problem with deploying a Matlab program to a different platform/architecture which only has a runtime version of Matlab installed.

My Matlab program was developed on a Windows platform, let's call it myprog.m. Now I want to run the program on a Sun Solaris Sparc server that has what I think is a Matlab Runtime Server / Runtime Environment.

I have converted my program to myprog.p using the pcode Matlab function, but after running it on the Sun server (as explained below), I get the error message

??? myprog.p is not a matlab p-file

The Sun server has another Matlab program, a p-file - other.p, which runs ok. To run it, I just enter 'matlab' on the command line. other.p has a companion file named matlabrt.p which I understand is run by the runtime engine, and in turn runs other.p.

matlab -> matlabrt.p -> other.p

I don't have my own matlabrt.p, so the above error message came after renaming myprog.p to other.p (so the error message actually wrote 'other.p' instead of 'myprog.p'). So what is wrong with my p-file?

I have read there are two different kinds of p-files. One is for use on a full Matlab installation, while the other works on the runtime engine. Further, the two has different encryption to make them work only as meant, i.e. in their intended environment. I guess my p-file is of wrong type.

I could use the Matlab compiler to deploy my program, but I currently only have a full Matlab license on the Windows platform. I therefor cannot compile for the Sun machine.

Tech guys say I cannot run p-code on a runtime environment type installation as this is a no licensed version of Matlab, but running of the other p-file apparently works ok.

How can i create a p-file that will run on the runtime enging / runtime server?
From: Arne on 19 Jan 2010 09:20
I have now found out that Matlab Runtime Server is no longer supported in Matlab. The only way to run a Matlab program on a computer not running Matlab today, is by using Matlab Compiler - or go back to release R13SP2 (2003) for the Runtime Server support.

"Arne " <rndzv(a)removehotmail.com> wrote in message <hj2doh$dou$1(a)fred.mathworks.com>...
> This post is about a problem with deploying a Matlab program to a different platform/architecture which only has a runtime version of Matlab installed.
>
> My Matlab program was developed on a Windows platform, let's call it myprog.m. Now I want to run the program on a Sun Solaris Sparc server that has what I think is a Matlab Runtime Server / Runtime Environment.
>
> I have converted my program to myprog.p using the pcode Matlab function, but after running it on the Sun server (as explained below), I get the error message
>
> ??? myprog.p is not a matlab p-file
>
> The Sun server has another Matlab program, a p-file - other.p, which runs ok. To run it, I just enter 'matlab' on the command line. other.p has a companion file named matlabrt.p which I understand is run by the runtime engine, and in turn runs other.p.
>
> matlab -> matlabrt.p -> other.p
>
> I don't have my own matlabrt.p, so the above error message came after renaming myprog.p to other.p (so the error message actually wrote 'other.p' instead of 'myprog.p'). So what is wrong with my p-file?
>
> I have read there are two different kinds of p-files. One is for use on a full Matlab installation, while the other works on the runtime engine. Further, the two has different encryption to make them work only as meant, i.e. in their intended environment. I guess my p-file is of wrong type.
>
> I could use the Matlab compiler to deploy my program, but I currently only have a full Matlab license on the Windows platform. I therefor cannot compile for the Sun machine.
>
> Tech guys say I cannot run p-code on a runtime environment type installation as this is a no licensed version of Matlab, but running of the other p-file apparently works ok.
>
> How can i create a p-file that will run on the runtime enging / runtime server?
 | 
Pages: 1
Prev: Doblu-click on a cell in uitable?
Next: varargout{1:nargout}