From: (Walter Roberson)
Newsgroups: comp.soft-sys.matlab
Subject: Re: MatLab Compiler
Date: Thu, 28 Jun 2007 18:51:58 +0000 (UTC)
Organization: National Research Council Canada - Conseil national de rechereches Canada
Lines: 21
Message-ID: <f6100e$dhj$>
References: <ef5b10f.22@webcrossing.raydaftYaTP> <ef5b10f.26@webcrossing.raydaftYaTP> <f60fd6$ha4$> <ef5b10f.29@webcrossing.raydaftYaTP>
X-Trace: 1183056718 13875 (28 Jun 2007 18:51:58 GMT)
NNTP-Posting-Date: Thu, 28 Jun 2007 18:51:58 +0000 (UTC)
Originator: (Walter Roberson)
Xref: comp.soft-sys.matlab:416307

In article <ef5b10f.29@webcrossing.raydaftYaTP>,
Ender  <> wrote:

>> I know what files I need to give to the end user. That is not the
>problem at this time. The problem is the MCRInstaller.exe is too
>large to be sent electronically or at least it is from my end. The
>end user can't run the excutable indpendently without the
>MCRInstaller.exe, but I can't send the program because 76MB is too

Then your problem would not be solved if Matlab compiled everything
into one executable. Your executable would simply be 76 Mb larger
than it currently is (150 Mb for 7.4 I read.)

Mathworks isn't simply throwing junk into MCRInstaller.exe :
that's where the code is to actually *do* everything built-in.
You need that code to run -- whether the code all lives in one
file (your executable) or lives in two files (the part that is just your
program plus the runtime.)
  Prototypes are supertypes of their clones.           -- maplesoft