| Project newbie asks...well what about ENVI projects? [message #61645] |
Fri, 25 July 2008 07:27  |
jeffnettles4870
Messages: 111
Registered: October 2006
|
Senior Member |
|
|
Hi folks,
Just got ENVI 4.5 with IDL 7.....so i'm getting used to the workbench
now (yikes! - but so far so good). I'm doing this as a complete
newbie to the concept of IDL projects. I knew pre-Workbench IDL
versions had projects, but never really had a need for them so i
ignored the whole thing.
Now, however, i find myself writing a bunch of code that i want to
distribute to several people, and the idea of setting up a project
immediately starts to seem attractive. Here's the thing though....the
code i'm writing is for ENVI. Basically i've got a bunch of .pro
files that adds a new menu item to ENVI's main menu and then handles
all the commands on that new menu item. So I think the relevant
difference here between what i want to do and a normal (?) IDL project
is that I don't want all of my .pro files to end up compiled into one
big save file that you launch with a single command. I want to have
one save file created for each .pro file. Is that possible? Is it
possible to have the directory that the compiled code ends up in be
different than the directory where the .pro files are (but maintain
the directory structure)?
I also have a resources folder that contains text files, images,
spectral libraries, etc.....stuff that isn't code but still needs to
end up in the "output" directory where all the compiled code ends up.
In the alternative, should i be thinking about how i could write my
own "build" program, that searches for .pro files, calls SAVE for
them, etc. and then handles the resource directory?
Any suggestions would be great.
Thanks,
Jeff
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
