An alternative technique when doing forensic debugging and project rescues on "Other People's Code" is to start a blank project, add the main program, and build. It pulls in the well-referenced files (you'll likely need to do a locate for the first item in each subdirectory) then run to find the other missing files. Because it only adds a few files at a time, you might find the bad file faster.
There's also a useful utility by Barbara Peisch & me called "WhichOne.prg" that will attempt to compile each file in a project one at a time, so you can figure out which file it hangs up on. On Thu, Mar 26, 2015 at 7:34 PM, Ted Roche <[email protected]> wrote: > An alternative techni > > On Thu, Mar 26, 2015 at 4:21 PM, Kevin Cully > <[email protected]> wrote: >> Good point. I created a "Hello1.pjx" with a main program that does a "? >> TIME() + " Hello World!". I was able to build that into an Hello1.app. >> >> Perhaps I have some additional problems in the project. >> >> >> On 03/26/2015 04:14 PM, Ted Roche wrote: >>> >>> I would go with [A]. I've installed DosBox and copied over my old FPD26 >>> directory and was able to build a Hello, World project and generate an app. >>> So, I wouldn't blame DosBox, at least right off. Didn't you need a >>> distribution kit in order to generate Apps and EXEs? >> >> >> [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CACW6n4tYsPN5jLv8UYwG7tOC21Ur_41=zr=xtjvzdzymu+h...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
