From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] qt5: use ccache for building host code
Date: Mon, 5 Nov 2018 21:16:49 +0100 [thread overview]
Message-ID: <20181105211649.7da32747@gmx.net> (raw)
In-Reply-To: <20181105084934.0044782e@windsurf>
Hello Thomas,
On Mon, 5 Nov 2018 08:49:34 +0100, Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> Hello Peter,
>
> On Sun, 4 Nov 2018 22:46:38 +0100, Peter Seiderer wrote:
>
> > Thanks for the answer (you got it right)...., so in case I use the
> > buildroot-generated qmake I will always use ccache (if configured),
> > even if used outside of the buildroot build system, right?
>
> Well, in the context of Buildroot, qmake is essentially used to build
> code for the target, using the cross-compiler. In this case, ccache was
> already used, because invoking ccache is hidden inside the toolchain
> wrapper, so there's no way around it :-)
>
> However, I guess with the right qmake invocations, you can make it
> build code for the host as well. And then yes, in this case, I assume
> it would now start using ccache.
>
So host ccache usage will behave the same as target usage..., O.k.
> > The $(HOSTCC) is expanded at the sed command running time,
> > g++-base.conf will contain 'QMAKE_COMPILER=gcc' or
> > 'QMAKE_COMPILER=ccache gcc'...
> >
Ups, missed the context here, the above was only to be sure it is expanded
at configure time...
> > Not sure if this matters for some use cases...
And this should be at the context host ccache usage...
>
> What are you worried about? The fact that there is a space in the
> QMAKE_COMPILER variable value ?
No worries, you can add my:
Reviewed-by: Peter Seiderer <ps.report@gmx.net>
Regards,
Peter
>
> Best regards,
>
> Thomas
next prev parent reply other threads:[~2018-11-05 20:16 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
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 [this message]
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=20181105211649.7da32747@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