|
From: Leo B. <lb...@Br...> - 2000-03-16 23:34:31
|
Dave Barnett wrote:
> One suggestion I might make is that you do something similar to how
> we've done a few of our modules.
>
> 1. In the module file proj1, do setenv SYNOPSYS_VER "1999.10", and then
> just do module load Synopsys (i.e. don't specify a version here, use the
> default one supplied by the .version file).
> 2. Make your Synopsys/.version file look similar to this:
> #%Module1.0
> set ModulesVersion = "1999.05"
> if { [info exists env(SYNOPSYS_VER)] } {
> set ModulesVersion = $env(SYNOPSYS_VER)
> }
>
> When you do the above, the default module would be 1999.05 for everyone,
> except those who override it with the env var SNYOPSYS_VER (either
> manually 'cause they know what they're doing, or because proj1 does it
> for them).
Hello, Dave.
You're right, this seems to work. Gotta get the "=" out of
that set statement, though. ;-) I gotta get that csh syntax
out of my head, took me forever to figure out what the problem
was.
Also, to make the project modulefiles be the keepers of the
default software versions for the project, I do a "setenv
SYNOPSYS_VER 1999.10" or whatever inside the project modulefile
before loading the modules.
As a note, I think I've found a nasty little bug in modules
3.0.6-rko that prevents this from working. If you do a
% module switch Synopsys/1999.10 Synopsys/1999.05
all of the environment vars for Synopsys will be missing from
the environment. Can someone else verify this? Seems consistent
on this end. No such problem with version 2.2b, though.
Cheers,
- Leo
----------------------------------------------------------------------
Leo Butler Senior Engineer
Brocade Communications Phone: (408) 487-8096
1901 Guadalupe Parkway Fax: (408) 487-8090
San Jose, CA 95131 mailto:lb...@br...
|
