[ECOS] Cygwin startup problem with ecosenv.sh

[ECOS] Cygwin startup problem with ecosenv.sh

[Paul D. DeRocco]

This may be a Cygwin issue, but since it's happening with ecosenv.sh,
someone here must have the obvious answer.

ecosenv.sh is supposed to set ECOS_REPOSITORY and prepend a couple things to
PATH. It doesn't when I run it from my .bash_profile script. Even if I
manually run it with "/opt/ecos3/ecosenv.sh" (ecos3 is where I put the new
version), the variables don't get set. If I add "echo $PATH" to the end of
ecosenv.sh, I see the path is properly set, but returning from ecosenv.sh to
the prompt seems to undo it, as though running the script starts a new bash
process instead of running the script in the existing process.

I'm not a Cygwin, Linux or bash expert, but the fact that eCos comes with an
ecosenv.sh script implies that it is expected that setting these variables
is supposed to survive the termination of the script, or it would be pretty
useless.

Anyone have a clue? The only way I can get over this hump is to put these
variables into the Windows environment so that they're already set up when
rxvt starts bash. But I'm afraid that this will bite me somewhere else down
the road if I don't fix it properly.

--

Ciao,               Paul D. DeRocco
Paul                mailto:pderocco@ix.netcom.com


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] RE: Cygwin startup problem with ecosenv.sh

[Paul D. DeRocco]

> From: Paul D. DeRocco [mailto:pderocco@ix.netcom.com]
>
> This may be a Cygwin issue, but since it's happening with
> ecosenv.sh, someone here must have the obvious answer.
>
> ecosenv.sh is supposed to set ECOS_REPOSITORY and prepend a
> couple things to PATH. It doesn't when I run it from my
> .bash_profile script. Even if I manually run it with
> "/opt/ecos3/ecosenv.sh" (ecos3 is where I put the new version),
> the variables don't get set. If I add "echo $PATH" to the end of
> ecosenv.sh, I see the path is properly set, but returning from
> ecosenv.sh to the prompt seems to undo it, as though running the
> script starts a new bash process instead of running the script in
> the existing process.

Never mind. I found some bash docs, and way down the end was a mention of
using a period at the start of the command line to make it execute a script
in the current shell.

--

Ciao,               Paul D. DeRocco
Paul                mailto:pderocco@ix.netcom.com


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss