home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.sys.apple2      Discussion about Apple II micros      56,720 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 55,993 of 56,720   
   Tom Thumb to Tom Thumb   
   Re: ORCA/C and Prizm again   
   27 Dec 22 13:45:30   
   
   From: justliketomsthumbsblues@gmail.com   
      
   On Tuesday, December 27, 2022 at 11:07:12 AM UTC-5, Tom Thumb wrote:   
   > Hi all and Happy Holidays,    
   >    
   > I have desktop program made from a resource file, two header and two source   
   files that I usually compile and link with an exec and linker files from the   
   text shell so that:    
   >    
   > make =    
   >    
   > compile flagging.rez keep=flagging    
   > compile flagging.cc keep=flagging    
   > compile grid.cc keep=grid    
   >    
   > cmpl linkit    
   >    
   > linkit =    
   >    
   > grid    
   > flagging    
   > keep=flagging    
   >    
   > flagging.cc includes flagging.h and grid.h    
   > grid.cc includes grid.h    
   >    
   > I've tried using Prizm to be able to step through some code but I'm having   
   my difficulties.    
   >    
   > I can stop at a breakpoint and examine variables in a program with a single   
   src file, and a header file or two I guess, but I can only get it working to a   
   fashion with the above mentioned setup.    
   >    
   > I’ve tried a few things: using the ‘Set Options” from the compile and   
   link menus but it won't compile and link properly from the debug menu or the   
   run -> compile to disk menu item.    
   >    
   > The best I’ve come up with is using the compile menu, uncheck the link   
   option and compile each file seperately and then use the link menu, uncheck   
   the execute after linking option and the choose trace option in execute   
   options and then the execute    
   menu item. That seems to break at the breakpoint and variables are displayed   
   but doesn’t display an arrow in the source listing and stepping seems a bit   
   flaky. Then if I remove the beakpoint and save the file I need to recompile   
   that file and relink    
   the program again or the breakpoint will linger.    
   >    
   > Any advice on how to go about this with the above setup? I’ve been using   
   printf as it’s less tedious and I’ve only just figured out how to get as   
   far as I have.   
      
   Well I guess I got it. I added +d to compile grid.cc and flagging.cc, ran make   
   from command line then in prizm I set the execute trace option and that works.   
   I had tried a variation of that before but had trouble with it.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca