On Thu, Dec 19, 2013 at 09:57:38AM +, David Chisnall wrote:
>
> On 19 Dec 2013, at 09:40, Luigi Rizzo wrote:
...
> >> Oh, and when I do a build of LLVM/Clang on my laptop using Ninja, it takes
> >> about 3-5 minutes, whereas when I do it with our build system it takes
> >> about 15. When I
On 19 Dec 2013, at 09:40, Luigi Rizzo wrote:
>
>> If a command produces warning output but exits with success, then that
>> command's output is dumped to stdout (explicitly serialised by Ninja so that
>> it's never interleaved with another command's output).
>>
>> If a command exits with a fa
On Thu, Dec 19, 2013 at 1:18 AM, David Chisnall wrote:
> On 16 Dec 2013, at 21:35, Dimitry Andric wrote:
>
> > In any case, if anything like this is implemented, I would really prefer
> > something like CMake does, e.g. give you a percentage counter that
> > provides some information about how 'f
On 16 Dec 2013, at 21:35, Dimitry Andric wrote:
> In any case, if anything like this is implemented, I would really prefer
> something like CMake does, e.g. give you a percentage counter that
> provides some information about how 'far' the build is progressing.
I haven't seen this for a while, b
On Mon, Dec 16, 2013 at 10:35 PM, Dimitry Andric wrote:
> On 16 Dec 2013, at 19:46, Luigi Rizzo wrote:
> > The following is a proof-of-concept patch to make system builds
> > less chatty.
> >
> > It also has the nice side effect of showing more clearly
> > which rules are used during the build a
On 16 Dec 2013, at 19:46, Luigi Rizzo wrote:
> The following is a proof-of-concept patch to make system builds
> less chatty.
>
> It also has the nice side effect of showing more clearly
> which rules are used during the build and possibly help
> debugging the share/mk files and the individual Ma
On Mon, Dec 16, 2013 at 1:46 PM, Luigi Rizzo wrote:
> The following is a proof-of-concept patch to make system builds
> less chatty.
>
> It also has the nice side effect of showing more clearly
> which rules are used during the build and possibly help
> debugging the share/mk files and the indivi
The following is a proof-of-concept patch to make system builds
less chatty.
It also has the nice side effect of showing more clearly
which rules are used during the build and possibly help
debugging the share/mk files and the individual Makefiles.
The logic is the following:
the environment/make
