On 5/1/05, Dario Freni <[EMAIL PROTECTED]> wrote: > Although I probably am a somewhat "power" user, I don't want my screen > to stay freezed for 10 minutes to an indefinite bunch of hours. The > ideal solution would be to have a progress bar or an activity bar. But > the _total_ silence, IMVHO, isn't acceptable for a buildworld > procedure.
Could we detect the build progress by looking at what the directory the compiler is in from the builds output? IE: /usr/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc2.c ^^^^^^^^^^^^^^^^^---- Could somewhat give us a indication that its currently building gnu items /usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/net_write.c .... etc And setup a few areas to look/grep for. If we could look for 5-10 different areas as the build progresses we could build a somewhat "crude" progress meter. Scott -- FreeSBIE mailing list (http://www.freesbie.org)
