| How to modify my IDL library path? [message #57080] |
Thu, 29 November 2007 23:03  |
mystea
Messages: 16
Registered: October 2007
|
Junior Member |
|
|
Dear all,
I have been trying to install the famous textoidl utility into my
computer. In order to keep this add-on separate from the original
library, I made a directory /usr/local/itt/idl64/addon and I decide to
put all my add-ons into that directory.
It turns out that in most cases this will work. (namely, when I put
a .pro file in that directory), but if I put a whole directory under
that directory, IDL will not find the files. (e.g. when I extracted
all the textoidl files to /usr/local/itt/idl64/addon/textoidl, IDL
won't see them at all.)
For managing sake, I don't want to extract textoidl files to /usr/
local/itt/idl64/addon/. Is it possible to change IDL's searching path?
Besides, it seems that IDL can't recognize my addons as a "native"
routine. (i.e. I need to compile them before I call them, unlike other
utilities such as interpolation.) Is there a trick to fix this?
Thank you all.
Gene
|
|
|
|
| Re: How to modify my IDL library path? [message #57111 is a reply to message #57080] |
Mon, 03 December 2007 09:09  |
Paul Van Delst[1]
Messages: 1157
Registered: April 2002
|
Senior Member |
|
|
mystea wrote:
> Dear all,
>
> I have been trying to install the famous textoidl utility into my
> computer. In order to keep this add-on separate from the original
> library, I made a directory /usr/local/itt/idl64/addon and I decide to
> put all my add-ons into that directory.
>
> It turns out that in most cases this will work. (namely, when I put
> a .pro file in that directory), but if I put a whole directory under
> that directory, IDL will not find the files. (e.g. when I extracted
> all the textoidl files to /usr/local/itt/idl64/addon/textoidl, IDL
> won't see them at all.)
>
> For managing sake, I don't want to extract textoidl files to /usr/
> local/itt/idl64/addon/. Is it possible to change IDL's searching path?
>
> Besides, it seems that IDL can't recognize my addons as a "native"
> routine. (i.e. I need to compile them before I call them, unlike other
> utilities such as interpolation.) Is there a trick to fix this?
Here is my idl setup from my .bashrc:
# Setup idl
export RSI_DIR=/usr/local/rsi
export IDL_DIR=$RSI_DIR/idl
export IDL_PATH="<IDL_DEFAULT>"
. $IDL_DIR/bin/idl_setup.bash
export IDL_PATH=${IDL_PATH}:+\${HOME}/scripts/idl:+\${RSI_DIR}/user _contrib
export IDL_STARTUP=$HOME/scripts/idl/idl_startup.pro
I believe my "+\${RSI_DIR}/user_contrib" would be equivalent to your "/addon" directory.
Note the "+" to get IDL to search all teh subdirectories as well. After reading other
reponses, I'm not sure if the "\" escape char is needed or not.
BTW, I thought the accepted convention was a "user_contrib" directory as opposed to "addon"?
cheers,
paulv
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
