| Re: Paths in the Workbench [message #59561 is a reply to message #59471] |
Mon, 31 March 2008 14:43   |
Vince Hradil
Messages: 574
Registered: December 1999
|
Senior Member |
|
|
On Mar 31, 12:20 pm, David Fanning <da...@dfanning.com> wrote:
>> I have been trying to give it the benefit of the doubt. If I turn
>> every feature off (which is pretty much what I have done), then the
>> Workbench is a worse editor than the one in IDL 6.4 and with a memory
>> footprint 10-12 times its previous size. Please tell me there are some
>> redeeming features I've overlooked here. :-(
>
> Of course, I could "build" my project, which works spectacularly
> if I have been careful to write all my project programs as procedures.
> But heaven help you if you thought you needed a function. There is
> no way on God's green Earth you are even going to get *that* project
> to
> build correctly.
>
> I see there is a provision for specifying your own custom build
> command, but
> I can't find hide nor hair of an example that would explain how you
> might do so. :-(
>
> Cheers (but not very cheery, this morning),
>
> David
David,
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'
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
