[build2] Handling of skipped files

[Moldmann Max (DC-MH/ENG52-NA)]

Awesome, I like it.
> skipped updating 17 target(s)

A minor detail: I think " skipped updating 17 targets" would be better.
Even "skipped updating 1 targets" doesn't feel too bad and it makes the output less noisy without the braces.

I'm fine with not seeing what exactly is being skipped and resorting to "b -v" to get more verbose information about that. But some people might like an option to get the skipped files listed after the actually compiled files (this would be an improvement over the old interwoven output).

Thanks a lot!
Max


-----Original Message-----
From: Boris Kolpackov [mailto:boris at codesynthesis.com] 
Sent: Tuesday, November 21, 2017 5:57 AM
To: Moldmann Max (DC-MH/ENG52-NA) <Max.Moldmann at boschrexroth-us.com>
Cc: users at build2.org
Subject: Re: [build2] Handling of skipped files

Hi Max,

Sorry for the late reply.

Moldmann Max (DC-MH/ENG52-NA) <Max.Moldmann at boschrexroth-us.com> writes:

> For a better, quicker overview of what the build does - might it be an 
> idea to print out all the skips first before the files that get compiled?
> Also maybe you could just summarize e.g. "117 skips" and then list the 
> actually compiled files. And only a verbose mode would show the list 
> of skipped files.

Yes, I agree, having all those "skips" interleaved with the actual compilation commands is not very useful.

I've changed build2 to:

1. Print the skip count in progress.

2. Print a one-line summary of skip count at the end.

Can you give it a try (the staged version) and see how it feels?

Thanks,
Boris