>>>>When the project manager compiles and exe, it seems to run through all the modules. Then it builds an app and then an exe. Why can it not only process the last file I changed, update the app / exe with that change? Anyone know exactly what it's doing to create the app and then the exe?
>>>
>>>It goes through all of them but for most of them it doesn't really recompile unless you tell it to (checkbox in the dialog or RECOMP keyword). On slower machines... ahem, 15 years ago, you could see the difference in the speed.
>>
>>We have a large project. If I can see it going through all of the files, that's a difference in speed, versus not wasting my time.
>
>Keeping the debugger closed makes it even faster...

True. But similar to C/C++, compile time can be inflated hugely via #include files, if a "kitchen sink" methodology is used in really large projects. When on P3 CPU with such a concept reached compile times >80 minutes for "recompile all", just turning the concept around to only include common or "system" includes in each branch project cut compile times to under 30 min. Back then I learned the hard way to heed the innocent warning of
"The maximum number of compiler levels for #INCLUDE is 4."
and to include the path of include file in include statement, as their path also was aiming to be humongous...