From: Ender <jr147@msstate.edu>
Path: news.mathworks.com!newsfeed-00.mathworks.com!webcrossing
Newsgroups: comp.soft-sys.matlab
Subject: Re: MatLab Compiler
Message-ID: <ef5b10f.26@webcrossing.raydaftYaTP>
Date: Thu, 28 Jun 2007 09:24:32 -0400
References: <ef5b10f.-1@webcrossing.raydaftYaTP> <ef5b10f.21@webcrossing.raydaftYaTP> <ef5b10f.22@webcrossing.raydaftYaTP> <ef5b10f.24@webcrossing.raydaftYaTP> <f5uhat$sce$1@canopus.cc.umanitoba.ca>
Lines: 53
NNTP-Posting-Host: 128.158.209.36
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Xref: news.mathworks.com comp.soft-sys.matlab:416226


Walter Roberson wrote:
>
>
> In article <ef5b10f.24@webcrossing.raydaftYaTP>,
> Ender <jr147@msstate.edu> wrote:
>
>>Could you explain what this means. How is it easier to have a
>>compiled excutable draw on the functions in the Matlab Component
>>Runtime environment, than to have to code all those functions
>>separately into the executable. I thought the executable was my
>>compiled code. I also understand that my executable will perform
> the
>>actions that are written into the compiled program, but I am
> confused
>>about what you said about the MatLab component Runtime part. I
> don't
>>have much experience compiling functions so if you could clarify
> this
>>for me please do.
>
> If you only have one compiled matlab application installed on a
> system,
> then the two possibilities are pretty much equivilent. If, however,
> you want to have two or more compiled matlab applications installed
> on the same system, then the bulk of the matlab runtime
> (all the built-in features) would end up compiled into each of
> the executables in what you propose -- which would needlessly
> duplicate
> that functionality. So to make it efficient to have multiple
> compiled Matlab applications on the same system Mathworks compiles
> your code down into a bunch of calls to the Matlab innards, and it
> shares a single copy of those Matlab innards between all the
> different
> compiled matlab applications [that are compiled with the same
> Matlab
> version.]
>
> If everything were to get merged into one executable so that there
> would be only one thing for you to send, then that one executable
> would end up being 150 Mb plus the size of whatever your part was.
> --
> "law -- it's a commodity"
> -- Andrew Ryan (The Globe and Mail,
> 2005/11/26)
>

This means that I cannot run MatLab code on a machine that does not
already contain MatLab. More specifically a machine that contains the
same version of MatLab that I compiled the code with. Unless there is
a website that I could down the MCRInstaller.exe for the version of
MatLab that I am using. If the first case that I mentioned is true,
then compiling a code is only good for systems of MatLab that are on
the same system because they will share the same version.