| Re: auto-compile [message #49402] |
Mon, 24 July 2006 09:55  |
JD Smith
Messages: 850
Registered: December 1999
|
Senior Member |
|
|
On Fri, 21 Jul 2006 15:52:50 -0700, Robbie wrote:
> Ideally, we should be able to specify a compiler directive at the top
> of a .pro file to indicate that RESOLVE_ROUTINE should compile the
> specified dependancy.
>
> In practice, I tend to arrange my code into modules which live in
> separate directories. I tend to compile directories rather than
> individual files. For example, you might have a few different
> algorithms which are invoked by CALL_FUNCTION. I'd recommend keeping
> those in a module (subdirectory).
Those get taken care of in my library, it's when they occur elsewhere,
including the IDL !DIR/lib library, that it's a problem.
> My trick for IDL library routines is to use UNIX soft links. I just
> create a directory which contains soft links to the IDL library
> routines of interest. I used to have a IDLgrObjects module directory
> for all graphics atoms, but I think that iTools resolve all takes care
> of that now.
And how do you discover which of these are being called indirectly via a
CALL_*? Right now I use the "wait for it to break" method, which isn't
ideal.
JD
|
|
|
|
|
|
| Re: auto-compile [message #49508 is a reply to message #49402] |
Tue, 01 August 2006 02:52  |
greg michael
Messages: 163
Registered: January 2006
|
Senior Member |
|
|
I gradually accumulate a make file with a list of .compile xxx lines in
it and a save,/routines at the end, which I copy and paste into the
IDLDE to do the compilation. This also relies on the 'wait for it to
break' method, but at least I know that any routine that's ever been
called during development ends up there. I'd rather use a better method
if anybody knows one...
Greg
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
