| 1 |
Am Freitag, 4. Mai 2012, 14:41:42 schrieb Mike Gilbert: |
| 2 |
> On Fri, May 4, 2012 at 2:29 PM, hasufell <hasufell@g.o> wrote: |
| 3 |
> > On 05/04/2012 08:00 PM, Johannes Huber wrote: |
| 4 |
> >> Am Freitag, 4. Mai 2012, 18:30:10 schrieb hasufell: |
| 5 |
> >>> # @ECLASS-VARIABLE: CMAKE_VERBOSE # @DESCRIPTION: # Set to enable |
| 6 |
> >>> verbose messages during compilation. |
| 7 |
> >>> |
| 8 |
> >>> By default this is deactivated which is inconvenient imo and |
| 9 |
> >>> results in pastes having minimum information. I have to tell |
| 10 |
> >>> users every time to recompile with CMAKE_VERBOSE=1 so that I have |
| 11 |
> >>> proper information on what is going on. |
| 12 |
> >>> |
| 13 |
> >>> Are there any arguments against this being default? |
| 14 |
> >> |
| 15 |
> >> In 95-99% of the build failures we get in kde herd the information |
| 16 |
> >> is sufficient. So from my point of view the current behaviour is |
| 17 |
> >> good. |
| 18 |
> >> |
| 19 |
> >> Greetings |
| 20 |
> > |
| 21 |
> > I think that as an argument pro CMAKE_VERBOSE=1 because that would |
| 22 |
> > cover 100% instead of 95-99. |
| 23 |
> |
| 24 |
> I only maintain a couple of cmake-based ebuilds, but I find having the |
| 25 |
> full compiler command line useful. Without it, I have to guess at what |
| 26 |
> was actually run. |
| 27 |
|
| 28 |
How about bump docs for that use case? For example |
| 29 |
http://www.gentoo.org/proj/en/qa/backtraces.xml |
| 30 |
|
| 31 |
Cheers |
| 32 |
-- |
| 33 |
Johannes Huber (johu) |
| 34 |
Gentoo Linux Developer / KDE Team |
| 35 |
GPG Key ID F3CFD2BD |
Archives