Thread Subject:

why does startup.m gets compiled along with the rest of the code?

Hello
When I compile a code that is in separate directory, I see
that even my startup.m file also gets compiled along with
it..
Why is it so? and How do I avoid doing that?
I really dont see any significance of the startup.m file
being compiled along with the rest of my code..
P.N: OS is Windows XP Matlab ver R2006b.

Vihang

"Vihang Patil" <vihang_patil@yahoo.com> wrote in message
<fs0fra$qie$1@fred.mathworks.com>...
> Hello
> When I compile a code that is in separate directory, I
see
> that even my startup.m file also gets compiled along
with
> it..
> Why is it so? and How do I avoid doing that?
> I really dont see any significance of the startup.m file
> being compiled along with the rest of my code..
> P.N: OS is Windows XP Matlab ver R2006b.
>
> Vihang

We usually suppress startup.m during compiling by simply
renaming it "suppress_startup.m" and also add the path to
the compile_targets directory.

Scott

"Scott Burnside" <no@spam.com> wrote in message
<fs122g$hrs$1@fred.mathworks.com>...
> "Vihang Patil" <vihang_patil@yahoo.com> wrote in message
> <fs0fra$qie$1@fred.mathworks.com>...
> > Hello
> > When I compile a code that is in separate directory, I
> see
> > that even my startup.m file also gets compiled along
> with
> > it..
> > Why is it so? and How do I avoid doing that?
> > I really dont see any significance of the startup.m file
> > being compiled along with the rest of my code..
> > P.N: OS is Windows XP Matlab ver R2006b.
> >
> > Vihang
>
> We usually suppress startup.m during compiling by simply
> renaming it "suppress_startup.m" and also add the path to
> the compile_targets directory.
>
> Scott

But then this is not really a workaround. And this is a
serious bug which needs to be resolved by TMW.
Vihang

"Vihang Patil" <vihang_patil@yahoo.com> wrote in message
<fs27cv$ppo$1@fred.mathworks.com>...
> "Scott Burnside" <no@spam.com> wrote in message
> <fs122g$hrs$1@fred.mathworks.com>...
> > "Vihang Patil" <vihang_patil@yahoo.com> wrote in
message
> > <fs0fra$qie$1@fred.mathworks.com>...
> > > Hello
> > > When I compile a code that is in separate directory,
I
> > see
> > > that even my startup.m file also gets compiled along
> > with
> > > it..
> > > Why is it so? and How do I avoid doing that?
> > > I really dont see any significance of the startup.m
file
> > > being compiled along with the rest of my code..
> > > P.N: OS is Windows XP Matlab ver R2006b.
> > >
> > > Vihang
> >
> > We usually suppress startup.m during compiling by
simply
> > renaming it "suppress_startup.m" and also add the path
to
> > the compile_targets directory.
> >
> > Scott
>
> But then this is not really a workaround. And this is a
> serious bug which needs to be resolved by TMW.
> Vihang

I was wondering about the same thing some time ago. Can't
remember why and how, but I came to conclution that it is
on purpose.
My workaround (propably suggested somewhere...) was to skip
most of my startup if compiled by isdeployed, which is more
or less (I guess) meant for such cases..
My startup.m:
if (~isdeployed) % do nothing if compiled
    most of the code, all actually
end

"Pekka " <pekka.nospam.kumpulainen@tut.please.fi> wrote in
message <fs84bm$ce8$1@fred.mathworks.com>...
> "Vihang Patil" <vihang_patil@yahoo.com> wrote in message
> <fs27cv$ppo$1@fred.mathworks.com>...
> > "Scott Burnside" <no@spam.com> wrote in message
> > <fs122g$hrs$1@fred.mathworks.com>...
> > > "Vihang Patil" <vihang_patil@yahoo.com> wrote in
> message
> > > <fs0fra$qie$1@fred.mathworks.com>...
> > > > Hello
> > > > When I compile a code that is in separate
directory,
> I
> > > see
> > > > that even my startup.m file also gets compiled
along
> > > with
> > > > it..
> > > > Why is it so? and How do I avoid doing that?
> > > > I really dont see any significance of the
startup.m
> file
> > > > being compiled along with the rest of my code..
> > > > P.N: OS is Windows XP Matlab ver R2006b.
> > > >
> > > > Vihang
> > >
> > > We usually suppress startup.m during compiling by
> simply
> > > renaming it "suppress_startup.m" and also add the
path
> to
> > > the compile_targets directory.
> > >
> > > Scott
> >
> > But then this is not really a workaround. And this is a
> > serious bug which needs to be resolved by TMW.
> > Vihang
>
> I was wondering about the same thing some time ago.
Can't
> remember why and how, but I came to conclution that it
is
> on purpose.
> My workaround (propably suggested somewhere...) was to
skip
> most of my startup if compiled by isdeployed, which is
more
> or less (I guess) meant for such cases..
> My startup.m:
> if (~isdeployed) % do nothing if compiled
> most of the code, all actually
> end
>

Thanks Pekka
I have used your recommendation "if (~isdeployed)" in my
startup.m file.
Regards
Vihang