From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] qt5base: use ccache if enabled
Date: Thu, 28 Nov 2013 23:11:35 +0100 [thread overview]
Message-ID: <87eh60xjl4.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1384436438-2119-2-git-send-email-fatih.asici@gmail.com> ("Fatih Aşıcı"'s message of "Thu, 14 Nov 2013 15:40:38 +0200")
>>>>> "Fatih" == Fatih A??c? <fatih.asici@gmail.com> writes:
> For now, it doesn't use ccache when compiling host tools (e.g. qmake).
> It seems the fix is not trivial.
> Signed-off-by: Fatih A??c? <fatih.asici@gmail.com>
> ---
> package/qt5/qt5base/qt5base-0002-mkspecs-files.patch | 6 +++++-
> package/qt5/qt5base/qt5base.mk | 1 +
> 2 files changed, 6 insertions(+), 1 deletion(-)
> diff --git a/package/qt5/qt5base/qt5base-0002-mkspecs-files.patch b/package/qt5/qt5base/qt5base-0002-mkspecs-files.patch
> index 3fddeac..6fa8a92 100644
> --- a/package/qt5/qt5base/qt5base-0002-mkspecs-files.patch
> +++ b/package/qt5/qt5base/qt5base-0002-mkspecs-files.patch
> @@ -14,9 +14,13 @@ Index: b/mkspecs/devices/linux-buildroot-g++/qmake.conf
> ===================================================================
> --- /dev/null
> +++ b/mkspecs/devices/linux-buildroot-g++/qmake.conf
> -@@ -0,0 +1,11 @@
> +@@ -0,0 +1,15 @@
> +include(../common/linux_device_pre.conf)
> +
> ++# modifications to g++.conf
> ++QMAKE_CC = $${BUILDROOT_CCACHE} $${QMAKE_CC}
> ++QMAKE_CXX = $${BUILDROOT_CCACHE} $${QMAKE_CXX}
> ++
> +#modifications to gcc-base.conf
> +QMAKE_CFLAGS += $${BUILDROOT_COMPILER_CFLAGS}
> +QMAKE_CXXFLAGS += $${BUILDROOT_COMPILER_CXXFLAGS}
> diff --git a/package/qt5/qt5base/qt5base.mk b/package/qt5/qt5base/qt5base.mk
> index febdc9b..a1d5dba 100644
> --- a/package/qt5/qt5base/qt5base.mk
> +++ b/package/qt5/qt5base/qt5base.mk
> @@ -168,6 +168,7 @@ define QT5BASE_CONFIGURE_CMDS
> -nomake examples -nomake tests \
> -device buildroot \
> -device-option CROSS_COMPILE="$(TARGET_CROSS)" \
> + -device-option BUILDROOT_CCACHE="$(CCACHE)" \
Can't we just pass it in CROSS_COMPILE?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-11-28 22:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 13:40 [Buildroot] [PATCH 1/2] qt5base: use -device-option to set mkspec variables Fatih Aşıcı
2013-11-14 13:40 ` [Buildroot] [PATCH 2/2] qt5base: use ccache if enabled Fatih Aşıcı
2013-11-28 22:11 ` Peter Korsgaard [this message]
2013-11-29 7:10 ` Fatih Aşıcı
2013-11-29 8:14 ` Peter Korsgaard
2013-11-29 8:26 ` Fatih Aşıcı
2013-11-18 22:41 ` [Buildroot] [PATCH 1/2] qt5base: use -device-option to set mkspec variables Arnout Vandecappelle
2013-11-20 12:22 ` Fatih Aşıcı
2013-11-20 12:17 ` [Buildroot] [PATCH v2] " Fatih Aşıcı
2013-11-20 22:18 ` Arnout Vandecappelle
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=87eh60xjl4.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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