| Re: Paths in the Workbench [message #59558 is a reply to message #59471] |
Mon, 31 March 2008 15:11   |
Vince Hradil
Messages: 574
Registered: December 1999
|
Senior Member |
|
|
On Mar 31, 4:51 pm, David Fanning <da...@dfanning.com> wrote:
> Vince writes:
>> To use the custom build just create an idl batch file with the compile
>> commands and save it. Then point to that batch file for the custom
>> build.
>
>> For example, say you have a procedure called foo in foo.pro. You
>> could make a text file called compile_foo which may contain:
>> cd, 'c:\foodir'
>> PATH='c:\foodir;c:\neededbyfoodir;'+!PATH
>> .comp foo
>> resolve_all
>> save, /routines, file='foo.sav'
>
> I wish it were that simple. Unfortunately, this particular project
> contains upwards of 100 files, and most of those are objects,
> which RESOLVE_ALL doesn't care much for. :-(
>
> Cheers,
>
> David
>
> P.S. I have a feeling IDL 6.4 might be good for a few more
> years, no matter how much money we thrown into the ITTVIS
> coffers.
How did you compile your routines in 6.4? You can do it the same way
in 7.0, right? I'm confused about what has changed. If you manage
your own path, you can do everything just like you used to, no?
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
