C
cverbiest
Guest
Launching a prowin32 with some start-up parameters takes a few seconds when started from the command prompt or from a windows shortcut Launching a prowin32 from PDSOE run configurations introduces a lot of overhead, up to 10 minutes on our system (*). This overhead probably has it's use if you want to debug the session, but most of the time we just want to launch a prowin32 that takes some properties from the project definition. It would be nice if the was a quick run option that skipped the build and rcode scan. (*) I don't know exactly what is happening but when it occurs it involves scanning all rcode.
Continue reading...
Continue reading...