| 1 |
On Fri, May 4, 2012 at 2:29 PM, hasufell <hasufell@g.o> wrote: |
| 2 |
> On 05/04/2012 08:00 PM, Johannes Huber wrote: |
| 3 |
>> Am Freitag, 4. Mai 2012, 18:30:10 schrieb hasufell: |
| 4 |
>>> # @ECLASS-VARIABLE: CMAKE_VERBOSE # @DESCRIPTION: # Set to enable |
| 5 |
>>> verbose messages during compilation. |
| 6 |
>>> |
| 7 |
>>> By default this is deactivated which is inconvenient imo and |
| 8 |
>>> results in pastes having minimum information. I have to tell |
| 9 |
>>> users every time to recompile with CMAKE_VERBOSE=1 so that I have |
| 10 |
>>> proper information on what is going on. |
| 11 |
>>> |
| 12 |
>>> Are there any arguments against this being default? |
| 13 |
>> |
| 14 |
>> In 95-99% of the build failures we get in kde herd the information |
| 15 |
>> is sufficient. So from my point of view the current behaviour is |
| 16 |
>> good. |
| 17 |
>> |
| 18 |
>> Greetings |
| 19 |
>> |
| 20 |
> |
| 21 |
> I think that as an argument pro CMAKE_VERBOSE=1 because that would |
| 22 |
> cover 100% instead of 95-99. |
| 23 |
> |
| 24 |
|
| 25 |
I only maintain a couple of cmake-based ebuilds, but I find having the |
| 26 |
full compiler command line useful. Without it, I have to guess at what |
| 27 |
was actually run. |
Archives