[Dart] compile output

[Bill Hoffman]

How do you specify the option?
I think the default should be that you see what it is actually doing,
perhaps with a --quiet option that you can give to the tcl script.
The "."'s do not mean much to me.


-Bill


At 12:01 PM 1/22/2002 -0500, Blezek, Daniel J (CRD) wrote:
>Agreed,  I added a Dart Option to give verbose build information.  Testing now.
>-dan
>
>> -----Original Message-----
>> From: Miller, James V (CRD) 
>> Sent: Tuesday, January 22, 2002 11:56 AM
>> To: Blezek, Daniel J (CRD); 'Brad King'; dart at public.kitware.com
>> Subject: RE: [Dart] compile output
>> 
>> 
>> I would prefer the build log to be displayed.  With the build 
>> log I can determine how far along I am in the build (if I am 
>> familar with the project).  With the dots, all I know is that 
>> something is happening....
>> 
>> 
>> 
>> -----Original Message-----
>> From: Blezek, Daniel J (CRD) 
>> Sent: Tuesday, January 22, 2002 11:46 AM
>> To: 'Brad King'; dart at public.kitware.com
>> Subject: RE: [Dart] compile output
>> 
>> 
>> In the sweeping changes that I plan to check in later today, 
>> I added a progress meter to the
>> Build.tcl step.  Rather than spit out the build log (which I 
>> think is irrelevant), a series of dots
>> sweep across the screen indicating how much of the build log 
>> has been generated.
>> 
>> Per your suggestion: It would require a lot more work to 
>> determine when each file has been compiled
>> in a platform independant way.  I know that the Microsoft 
>> compile currently puts a nice line at the
>> beginning of each step, and CMake could write makefiles the 
>> same way, but I would rather have a look
>> at the build log directly, and keep Dart's output limited to 
>> status/progress information.
>> 
>> What do you think?
>> -dan
>> 
>> > -----Original Message-----
>> > From: Brad King [mailto:brad.king at kitware.com]
>> > Sent: Tuesday, January 22, 2002 11:11 AM
>> > To: dart at public.kitware.com
>> > Subject: RE: [Dart] compile output
>> > 
>> > 
>> > > Great suggestion!  [read stdin] isn't the best thing, as it 
>> > will block
>> > > until the process is done, and then spit out the whole 
>> thing, but we
>> > > can make this work...  I'm on it...
>> > Can't we just capture the output in a Tcl variable after each 
>> > step runs,
>> > and then do a puts to stdout and also write it to the log?  
>> This seems
>> > like a simpler implementation for the same behavior.
>> > 
>> > -Brad
>> > 
>> > _______________________________________________
>> > Dart mailing list
>> > Dart at public.kitware.com
>> > http://public.kitware.com/mailman/listinfo/dart
>> > 
>> _______________________________________________
>> Dart mailing list
>> Dart at public.kitware.com
>> http://public.kitware.com/mailman/listinfo/dart
>> 
>_______________________________________________
>Dart mailing list
>Dart at public.kitware.com
>http://public.kitware.com/mailman/listinfo/dart