marble builds when it shouldn't

[Ben Cooksley]

On Wed, Sep 23, 2015 at 7:25 AM, Scarlett Clark
<scarlett.gately.clark at gmail.com> wrote:
> That is correct. I have turned this off and on so many times it is not
> funny. Somehow everyone needs to agree on this.

The issue primarily boils down to build log size, especially for the
larger projects which take a long time to build - like Calligra, KDE
PIM, etc.

It doesn't appear to be a large issue - however the logs are >100mb
per build, and when you store the last 50 builds this quickly adds up
into a large user of disk space (especially when you consider the
number of projects we have - you could easily be looking at 100gb+ of
build logs and other materials ). This means we basically have to skip
backups (which previously was a problem - because it wasn't generated
from anywhere, now it's less of an issue).

The verbose build logs also tend to be harder to follow when you're
watching a build.

> Scarlett

Cheers,
Ben

>
>
> On Tue, Sep 22, 2015 at 12:24 PM, Jan Kundrát <jkt at kde.org> wrote:
>>
>> On Tuesday, 22 September 2015 13:00:38 CEST, Harald Sitter wrote:
>>>
>>> Also on a more general note: I think it would be handy if all builds
>>> used CMAKE_VERBOSE_MAKEFILE=TRUE to get verbose make output which
>>> would make it easier to notice when things such as -DNDEBUG are passed
>>> to gcc.
>>
>>
>> Absolutely -- the last time I raised this, though, someone disagreed on
>> basis of increased volume of logs, IIRC.
>>
>> With kind regards,
>> Jan
>>
>> --
>> Trojitá, a fast Qt IMAP e-mail client -- http://trojita.flaska.net/
>> _______________________________________________
>> Kde-frameworks-devel mailing list
>> Kde-frameworks-devel at kde.org
>> https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
>
>
>
> _______________________________________________
> Kde-frameworks-devel mailing list
> Kde-frameworks-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
>