You have to run "source" rather than "csh" on the setup files. Source
runs it *in* the current shell, so environment variables set by the
script are still set once it exits. "csh" creates a new shell, so any
env vars set in that shell go away when the command does.
So...
setenv V2TOP /where/ever/...
source $V2TOP/vicset1.csh
source $V2TOP/vicset2.csh
If source doesn't work, you're probably using bash as a shell. Switch
to csh (or better yet, tcsh), should be a simple:
tcsh
to do that.
(If you really really want to use bash instead of csh, if you do csh or
tcsh, and run the setups, and then invoke another shell via "bash" then
the env vars should be inherited and you're (mostly) good to go.
However, we strongly recommend using csh/tcsh with VICAR).
Hope that helps...
-Bob
> --
> You received this message because you are subscribed to the Google
> Groups "VICAR Open Source" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
vicar-open-sou...@googlegroups.com
> <mailto:
vicar-open-sou...@googlegroups.com>.
> To post to this group, send email to
vicar-op...@googlegroups.com
> <mailto:
vicar-op...@googlegroups.com>.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/vicar-open-source/727d7e79-abb9-4954-8869-18cf7faa19e1%40googlegroups.com
> <
https://groups.google.com/d/msgid/vicar-open-source/727d7e79-abb9-4954-8869-18cf7faa19e1%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit
https://groups.google.com/d/optout.