1 |
Am Freitag, 4. Mai 2012, 18:30:10 schrieb hasufell: |
2 |
> # @ECLASS-VARIABLE: CMAKE_VERBOSE |
3 |
> # @DESCRIPTION: |
4 |
> # Set to enable verbose messages during compilation. |
5 |
> |
6 |
> By default this is deactivated which is inconvenient imo and results in |
7 |
> pastes having minimum information. |
8 |
> I have to tell users every time to recompile with CMAKE_VERBOSE=1 so |
9 |
> that I have proper information on what is going on. |
10 |
> |
11 |
> Are there any arguments against this being default? |
12 |
|
13 |
I think the resistance against this more has to do with the output being more |
14 |
esthetically pleasing (yes I know this is not really a good point for us, but |
15 |
in general the cmake output is quite nice) than with "writing to stdout is |
16 |
expensive" (which was a joke in the previous thread). |
17 |
|
18 |
That being said, it probably makes sense to change the default to =1, as it |
19 |
definitely helps debugging to see the build commands. |
20 |
|
21 |
@infra: |
22 |
However, please raise the file size limit for bugzilla then, and if possible, |
23 |
please fix the use of compressed build logs. Right now, I would not recommend |
24 |
uploading a compressed log to bugzilla, because: |
25 |
* I have not found a way to have firefox uncompress and display it correctly |
26 |
with one click (always have to download, save, ...) |
27 |
* and often files end up double-compressed, i.e. save log.gz, gunzip, rename |
28 |
log to log.gz, gunzip :( |
29 |
|
30 |
Cheers, Andreas |
31 |
|
32 |
-- |
33 |
Andreas K. Huettel |
34 |
Gentoo Linux developer |
35 |
kde (team lead), sci, tex, arm, printing |
36 |
dilfridge@g.o |
37 |
http://www.akhuettel.de/ |