Bug 130076 - [GTK][CMAKE] Too verbose build output
Summary: [GTK][CMAKE] Too verbose build output
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Martin Robinson
Keywords: Gtk
Depends on:
Reported: 2014-03-11 01:58 PDT by Carlos Garcia Campos
Modified: 2014-03-12 08:49 PDT (History)
3 users (show)

See Also:

Patch (3.46 KB, patch)
2014-03-11 19:12 PDT, Martin Robinson
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Carlos Garcia Campos 2014-03-11 01:58:46 PDT
When building using ninja, the output is too verbose for some targets, where we previously had GEN foo now we have several lines of noise. 

Another problem is that when ninja is run by cmake, the smart terminal features don't work, so all the output is written using a new line and we loose the nice colors when using icecc, for example. This is because ninja doesn't write directly to the terminal, but to a cmake pipe (or whatever, I don't know), and isatty(1) returns false and ninja disables the smart terminal features. I wonder if we could run cmake first to generate the build.ninja file and then run ninja ourselves from build-webkit instead of using cmake. 

So, if we can use the default ninja output suing the smart terminal features, the verbose target wouldn't be a problem. I still think we should produce less verbose output for the bots, though.
Comment 1 Martin Robinson 2014-03-11 19:12:23 PDT
Created attachment 226464 [details]
Comment 2 Carlos Garcia Campos 2014-03-12 01:10:58 PDT
Comment on attachment 226464 [details]

View in context: https://bugs.webkit.org/attachment.cgi?id=226464&action=review

This works great, I still would like that verbose targets use something like Generating Foo for the cases where smart terminal is not used like in the bots logs. Thanks.

> Source/cmake/OptionsGTK.cmake:311

I wonder why you need to first write in one directory and then copy to another, but I have no idea how cmake works :-P
Comment 3 Martin Robinson 2014-03-12 08:44:25 PDT
(In reply to comment #2)

> I wonder why you need to first write in one directory and then copy to another, but I have no idea how cmake works :-P

This is the only way I could find to change the permissions of a file without resorting to a shell command, unfortunately.
Comment 4 Martin Robinson 2014-03-12 08:48:50 PDT
Comment on attachment 226464 [details]

Clearing flags on attachment: 226464

Committed r165473: <http://trac.webkit.org/changeset/165473>
Comment 5 Martin Robinson 2014-03-12 08:49:46 PDT
All reviewed patches have been landed.  Closing bug.