[cmake-developers] Ninja: files per second

Shlomi Fish shlomif at shlomifish.org
Sat Jul 28 05:43:33 EDT 2012


Hi Peter,

thanks for your work on Ninja.

On Sat, 28 Jul 2012 10:57:44 +0200
Peter Kümmel <syntheticpp at gmx.net> wrote:

> I've added a nice feature to ninja which is now upstream:
> 
> By setting the environment variable NINJA_STATUS
> 
> bash:
>          export NINJA_STATUS="[%s/%t %o(%c)/s] "
> 
> cmd.exe (with space at the end):
> 
>          set NINJA_STATUS=[%s/%t %o(%c)/s]
> 
> Ninja prints the overall processed files per second and the
> the current rate of files per second (averaged over the last -j files).
> 
> For instance compiling cmake I get (-DCMAKE_BUILD_TYPE=Release):
> - Linux   gcc 4.6: [397/397 6.6(12)/s]
> - Windows gcc 4.7: [438/438 5.9(11)/s]
> - Mac     gcc 4.2: [462/462 4.9(3)/s]
> 

Nice.

I was now able to get the Freecell Solver test suite to pass with "ninja test",
but there is one problem: when I run "ninja -vv test", then ninja displays the
line 
"[1/1] cd /home/shlomif/progs/freecell/git/fc-solve/fc-solve/source/n &&
perl /home/shlomif/progs/freecell/git/fc-solve/fc-solve/source/run-tests.pl"

and then it waits for the entire test suite to run, and only then displays its
output. This is frustrating because I want to see the output while the test
suite is running. Is there anyway to do it like that?

Regards,

	Shlomi Fish

> See also
> https://github.com/martine/ninja/blob/master/doc/manual.asciidoc#environment-variables
> 
> Happy benchmarking,
> Peter
> --
> 
> Powered by www.kitware.com
> 
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
> 
> Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
> 
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers



-- 
-----------------------------------------------------------------
Shlomi Fish       http://www.shlomifish.org/
List of Portability Libraries - http://shlom.in/port-libs

* Backward compatibility is your worst enemy.
* Backward compatibility is your users’ best friend.

Please reply to list if it's a mailing list post - http://shlom.in/reply .



More information about the cmake-developers mailing list