Progress UI for Phases

[Ryan Schmidt]

On Oct 26, 2010, at 14:04, Jeremy Lavergne wrote:

>>> You could have make do a dry run where it doesn't build, then compare that list against where we are in the build output.
>> 
>> I didn't know it was possible to have "make" do a dry run.
> 
> man make:
>       -n, --just-print, --dry-run, --recon
>            Print  the  commands  that  would  be executed, but do not execute
>            them.
> 
> Just like how macports has all these special things that no one knows about: it's in the man page! :-)

Thanks, I briefly scanned the manpage but did not see that option. I see it now.

So that could possibly be used for the build and destroot phases. For the build phase, some trickery would have to be used when parallel building to match things up.

I wonder how long a dry run would take for a very large program, like qt4-mac.

These methods would only work for ports that build using a Makefile. Granted that's most of them, but it's not all of them.

How would we handle the configure phase? There's a lot of variation there. Some use autoconf-generated configure scripts, some use homegrown ones, some use cmake, some kick off long builds in the configure phase (like cmake itself)...