I think I may have something basically wrong in the way I am working with ENVI extensions. In IDL, I’ve created a linked project that points to my code in my development folder. When I’m ready to test it I copy the code over to the ENVI extensions folder: C:\Program Files\Harris\ENVI54\extensions When ENVI runs, it shows my project in the correct extensions folder and the project executes correctly. However, it also shows the list of the sub-procedures that project calls and flags an error for each of those sub-procedures that the sub-procedures are undefined. If I take those sub-procedures out of the ENVI extensions folder, then the project doesn’t execute because it doesn’t have the sub-procedures there. I also tried putting only the .sav file (created by the IDL build project command) into the ENVI extensions folder, but that .sav file also shows as undefined in ENVI This seems like I’m just doing something dumb…any advice would be appreciated.
|