| 1 |
On Fri, May 4, 2012 at 3:25 PM, Johannes Huber <johu@g.o> wrote: |
| 2 |
> Am Freitag, 4. Mai 2012, 14:41:42 schrieb Mike Gilbert: |
| 3 |
>> On Fri, May 4, 2012 at 2:29 PM, hasufell <hasufell@g.o> wrote: |
| 4 |
>> > On 05/04/2012 08:00 PM, Johannes Huber wrote: |
| 5 |
>> >> Am Freitag, 4. Mai 2012, 18:30:10 schrieb hasufell: |
| 6 |
>> >>> # @ECLASS-VARIABLE: CMAKE_VERBOSE # @DESCRIPTION: # Set to enable |
| 7 |
>> >>> verbose messages during compilation. |
| 8 |
>> >>> |
| 9 |
>> >>> By default this is deactivated which is inconvenient imo and |
| 10 |
>> >>> results in pastes having minimum information. I have to tell |
| 11 |
>> >>> users every time to recompile with CMAKE_VERBOSE=1 so that I have |
| 12 |
>> >>> proper information on what is going on. |
| 13 |
>> >>> |
| 14 |
>> >>> Are there any arguments against this being default? |
| 15 |
>> >> |
| 16 |
>> >> In 95-99% of the build failures we get in kde herd the information |
| 17 |
>> >> is sufficient. So from my point of view the current behaviour is |
| 18 |
>> >> good. |
| 19 |
>> >> |
| 20 |
>> >> Greetings |
| 21 |
>> > |
| 22 |
>> > I think that as an argument pro CMAKE_VERBOSE=1 because that would |
| 23 |
>> > cover 100% instead of 95-99. |
| 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. |
| 28 |
> |
| 29 |
> How about bump docs for that use case? For example |
| 30 |
> http://www.gentoo.org/proj/en/qa/backtraces.xml |
| 31 |
> |
| 32 |
|
| 33 |
As far as I can tell, such documentation is largely ignored unless |
| 34 |
users are pointed to it by a comment on a bug. It would be nice to |
| 35 |
avoid having to wait for the user to respond with the updated build |
| 36 |
log. |
Archives