Re: Extremely long build times

In article <xn0f9fbl09d2t3l001@xxxxxxxxxxxxxxxxxxxxxx>, Bruce McGee
says...

There is a free version of the tool I use to manage my uses clauses.
I've seen a difference on large projects.

Yes indeed - Icarus was instrumental in our being able to resolve the
initial problem and identify the vulnerable units.

Be aware however that the tool has some problems - we had to modify our
source in order for Icarus to be able to parse the project, including
using conditional symbols to exclude implementation code that the Icarus
parser choked on, using Icarus' project settings to exclude that code
when analyzing vs actually building, e.g.:

procedure Foo;
begin
{$ifndef ICARUS}
:
{$endif}
end;

Not a huge problem - only 2 such changes were needed - and once
"Icarusized" the project has not presented problems for the parser
since, but something to be aware of.


We found that the performance of Icarus doesn't really lend itself to
day-to-day use though, so we use it as needed as part of our project
forensics kit, rather than our day to day development tool chain.

Hence the "Red Flag" convention on check-ins.

--
JS
TWorld.Create.Free;
.