[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: problem executing code "saved" using SAVE command
Sorry about the html -- didn't realize that.
Anyway, I tried your compile routine. I was able to create the
main_gui.sav file. But it did not work because for some reason it
didn't recognize one of my functions (although it was compiled). One
explaination (maybe) is that I don't have the procedures compiled in a
strict order. For instance, a procedure may use another procedure that
was compiled after the first one. Also, the 'print,main_gui_info()' did
not work either.
Your suggestion of restoring the '.sav' file in the IDLDE was a good
one. I tried it. Sure enough it works like it is supposed to. So, I'm
still stuck with a working version when running from IDLDE, but problems
when running it as a run-time program.
Reimar Bauer wrote:
> Dear Tom,
> I have written a compile routine for idl.
> And we have had no problems with this compiled code.
> You should try this routine.
> idl > compile,'main_gui.pro'
> and additional a function inside is created
> shows all compiled and embedded pro and sav files.
> (last modification ,file /dir ...)
> !PATH is undefined during runtime
> execute won't work in runtime
> If my routine won't work I am interested to learn from you!
> p.s. better you don't post HTML
> "Thomas S. Spisz" wrote:
> > I have a problem with IDL code that I "saved" (compiled) using the
> > SAVE command -- it doesn't execute the same as the same code run
> > directly from the IDL Development Environment. (By the way, I do
> > realize that you can't really compile IDL code.) Let me explain the
> > situation. First of all, I'm on Windows NT machine, and IDL 5.4.
> > I have a set of procedures with one procedure called 'main_gui.pro'
> > that is the main procedure that calls other procedures. I can enter
> > IDL, compile 'main_gui.pro' and all it's necessary procedures. Then
> > type 'resolve_all', and run it -- it does beautifully.
> > However, if I enter IDL, compile 'main_gui.pro' and all it's necessary
> > procedures. Then type 'resolve_all'. Then type
> > "save, filename='c:\main_gui.sav', /routines" which saves everything
> > into that single binary file. When I double-click on 'main_gui.sav',
> > it does execute but not correctly. It leaves out certain plotting
> > commands and has some widget errors that shouldn't occur and do not
> > occur if run directly from IDL Development Environment as stated in
> > previous paragraph.
> > The real bummer is that I cannot debug this problem because when I
> > execute the 'main_gui.sav' file, then IDL is in run-time mode.
> > Therefore, I don't see the output log and cannot use any of the debug
> > capabilities in the IDL Development Environment.
> You can restore the file in the idl development and execute then
> If you see that's something additional is compiled then this is the
> why it's not working
> > Any knowledge or help with this problem is greatly appreciated.
> > Tom Spisz
> > Johns Hopkins University Applied Physics Laboratory
> > 11100 Johns Hopkins Road
> > Laurel, MD 20723-6099
> > 240-228-7260
> > firstname.lastname@example.org
> Reimar Bauer
> Institut fuer Stratosphaerische Chemie (ICG-1)
> Forschungszentrum Juelich
> email: R.Bauer@fz-juelich.de
> a IDL library at ForschungsZentrum Juelich
> read something about linux / windows