On Wed, 2 Feb 2005 01:48:02 -0600, Boyd Stephen Smith Jr. wrote: > While the wrapper could tell something about what it's doing, based on > the command-line, it can't tell you how many times gcc (for example) > will be invoked in the future. A wrapper for make won't be able to do > that either, because you have to parse the makefile to get an accurate > count.
There was a project on the forums that did something like this. It provided a replacement make that ran make in a pretend mode to get the count, then ran it again. The gcc output was then redirected to a file and all the user saw was a progress bar. It was a nice idea let down by the simple flaw that it completely screwed up some compilations. For example, when emerging transcode, it would build the executables, but the make install stage didn't install them :( You have to be very careful about hacking into the build process, which is why I now prefer something that just makes a guesstimate, like eprogress or genlop --current. -- Neil Bothwick An example of hard water is ice. -- [email protected] mailing list
