| Re: System Variable Behavior Changed in IDL 6.0 [message #38614 is a reply to message #38488] |
Thu, 11 March 2004 13:52   |
mperrin+news
Messages: 81
Registered: May 2001
|
Member |
|
|
Michael Wallace <mwallace.removethismunge@swri.edu.invalid> wrote:
>> just create two soft links:
>>
>> ln -s /usr/local/rsi/idl_5.5/bin/idl /usr/local/bin/idl55
>> ln -s /usr/local/rsi/idl_6.0/bin/idl /usr/local/bin/idl60
>>
>> and use the idl55 and idl60 commands (idl is a script itself, which sets
>> the appropriate env. variables).
>
> In this case, you still have the issue of what IDL_PATH is set to. If
> left unset, the soft links solution you suggest will work. IDL will
> automagically determine the correct lib directory to use.
>
> However, almost all of us have to explicitly set IDL_PATH in order to
> include our own libraries and other procedures. Because of this we are
> forced to choose between the $RSI_DIR/idl_5.5/lib directory and the
> $RSI_DIR/idl_6.0/lib directories. And you can't set IDL_PATH to include
> both directories since one will clobber the other.
>
> So, with that in mind, the better solution is to symlink the IDL
> directories rather than the executables. By using a symlink that points
> to idl_5.5 or idl_6.0 or other directory, we don't have the IDL_PATH
> issue because we just have to only include $RSI_DIR/idl/lib in IDL_PATH.
> So, all we have to do is change the symlink and we're ready to go.
Alternatively, one can just use environment variables:
-------
setenv IDL_DIR /usr/local/rsi/idl_6.0
#setenv IDL_DIR /usr/local/rsi/idl_5.6
setenv LM_LICENSE_FILE $IDL_DIR/license/license.dat
setenv IDL_PATH +$IDL_DIR/lib:+$HOME/idl
-------
Put this in your .tcshrc (or equivalent) and all you have to do is change
which of the first two lines is uncommented and then start a new shell.
- Marshall
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
