[vtkusers] REALLY long build time for vtk tcl wrappers

[anast.jm at pg.com]

I'm seeing something funny with a completely stock nightly Jun 16 vtk/tcl debug
non-incremental build...

At work with a dual 933Mhz PIII Xeon system with 1GB ram and a fast drive on
WinNT4sp6, vtk3.2 nightly built  with tcl bindings in about 30-45 minutes
(didn't check real close).

At home with 500mhz PIII, 256mb ram, Win98SE - vtk built in a couple of hours,
slow but reasonable I thought...however tcl bindings took 3 DAYS! The computer
was so tied up with the tcl build that the windows clock only updated a few
minutes a day and after a mouse move the cursor would move a small amount every
few minutes. A new module wrap would seem to build every 10-30 minutes or so.
tcl did build finally and it works. I didn't see alot of disk activity. System
response was so slow that I couldn't get in to see what was hogging all the cpu
time but I suspect based on Windows behavior that the build process had it all.
I decide to forgo my home email to see how long this might take (-:

Any idea whats going on here???    ....thanks, john