Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] qt5: use ccache for building host code
Date: Sun, 4 Nov 2018 22:08:51 +0100	[thread overview]
Message-ID: <20181104220851.7accc310@gmx.net> (raw)
In-Reply-To: <20181103144917.05c221c1@windsurf>

Hello Thomas,

On Sat, 3 Nov 2018 14:49:17 +0100, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:

> Hello Peter,
> 
> On Sat, 20 Oct 2018 15:25:35 +0200, Thomas Petazzoni wrote:
> > qt5 currently doesn't use HOSTCC/HOSTCXX, so it doesn't use ccache
> > when building all its host code (especially qmake). This means that
> > even with ccache enabled and a hot cache, it still takes a long time
> > to build qt5base.
> > 
> > Before this patch, building qt5base takes:
> > 
> >  - 446 seconds with a cold ccache
> >  - 185 seconds with a hot ccache
> > 
> > This is because the ccache is not used for host code.
> > 
> > After this patch, building qt5base takes:
> > 
> >  - 450 seconds with a cold ccache
> >  - 15 seconds with a hot ccache
> > 
> > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>  
> 
> Any comment on this patch ?

Sorry, not an regular ccache user (maybe an mistake ;-) ), so I did not
examine this patch yet, nice speedup, some questions at he patch reply...

Regards,
Peter

> 
> Thanks!
> 
> Thomas

  reply	other threads:[~2018-11-04 21:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-20 13:25 [Buildroot] [PATCH] qt5: use ccache for building host code Thomas Petazzoni
2018-11-03 13:49 ` Thomas Petazzoni
2018-11-04 21:08   ` Peter Seiderer [this message]
2018-11-04 21:12 ` Peter Seiderer
2018-11-04 21:25   ` Thomas Petazzoni
2018-11-04 21:46     ` Peter Seiderer
2018-11-05  7:49       ` Thomas Petazzoni
2018-11-05 20:16         ` Peter Seiderer
2018-11-30  9:00 ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181104220851.7accc310@gmx.net \
    --to=ps.report@gmx.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox